[jira] [Updated] (MESOS-1886) Allow docker pull on each run to be configurable

["Timothy Chen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MESOS-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Chen updated MESOS-1886:
--------------------------------
    Fix Version/s: 0.22.0

> Allow docker pull on each run to be configurable
> ------------------------------------------------
>
>                 Key: MESOS-1886
>                 URL: https://issues.apache.org/jira/browse/MESOS-1886
>             Project: Mesos
>          Issue Type: Improvement
>          Components: containerization
>    Affects Versions: 0.20.1
>            Reporter: Chris Heller
>            Assignee: Timothy Chen
>            Priority: Minor
>              Labels: docker
>             Fix For: 0.22.0
>
>
> With 0.20.1 the behavior of a docker container has changed (see MESOS-1762).
> This change brings the docker behavior more in line with that of {{docker run}}.
> I propose,if the image given explicitly has the ":latest" tag, this should signify to mesos that an unconditional `docker pull` should be done on the image... and if it should fail for any reason (i.e. the registry is unavailable) we fall back to the current behavior.
> This would break slightly with the semantics of how the docker command line operates, but the alternative is to require explicit tags on every release -- which is a hinderance when developing a new image, or one must log in to each node and run an explicit `docker pull`.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)