[
https://issues.apache.org/jira/browse/MESOS-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Hindman resolved MESOS-1770.
-------------------------------------
Resolution: Fixed
commit cc9fd81243bdcbf468a2d8cbcb22e6527335bf00
Author: Timothy Chen <[email protected]>
Date: Wed Sep 17 08:49:38 2014 -0700
Override entrypoint when shell enabled in Docker.
Review: https://reviews.apache.org/r/25403
> Docker with command shell=true should override entrypoint
> ---------------------------------------------------------
>
> Key: MESOS-1770
> URL: https://issues.apache.org/jira/browse/MESOS-1770
> Project: Mesos
> Issue Type: Improvement
> Reporter: Timothy Chen
> Assignee: Timothy Chen
> Labels: docker
> Fix For: 0.20.1
>
>
> Currently with the new CommandInfo there is a shell flag that if it's
> enabled, will wrap the command with /bin/sh -c with docker run.
> However we don't override the entrypoint, therefore when a user specified a
> image with a entrypoint and also have shell=true then /bin/sh -c will become
> part of the argument to the entrypoint.
> I don't think there is any example where users expect /bin/sh -c to be a
> argument in the entrypoint, and to make sure cases where shell is needed for
> expanding environment variables we also override the entrypoint.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
