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/11/04 19:23:34 UTC

[jira] [Assigned] (MESOS-1886) Always `docker pull` if explicit ":latest" tag is present

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

Timothy Chen reassigned MESOS-1886:
-----------------------------------

    Assignee: Timothy Chen

> Always `docker pull` if explicit ":latest" tag is present
> ---------------------------------------------------------
>
>                 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
>
> 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)