[
https://issues.apache.org/jira/browse/MESOS-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14165752#comment-14165752
]
Timothy Chen commented on MESOS-1886:
-------------------------------------
Hi [~ChrisHeller], I understand your context, but I think trying to bypass
frameworks is generally not what Mesos tries to do.
We try to allow explicit options that the framework choose to expose or not,
and that's a intentional choice and Mesos choose the sensible default action,
which we choose to be on par with docker run.
So I think based on this we want to provide an option for DockerInfo instead,
let me know what you think.
> 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
> 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)
