You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Timothy Chen (JIRA)" <ji...@apache.org> on 2014/09/05 23:29:28 UTC
[jira] [Updated] (MESOS-1770) Docker with command shell=true should
override entrypoint
[ https://issues.apache.org/jira/browse/MESOS-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Chen updated MESOS-1770:
--------------------------------
Target Version/s: 0.20.1
Shepherd: Benjamin Hindman
> 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
>
> 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)