[
https://issues.apache.org/jira/browse/MESOS-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14492609#comment-14492609
]
Adam Avilla commented on MESOS-1886:
------------------------------------
+1 to [~codecraig]'s comment.
Also, I am having a hard time figuring out how this is configured when creating
a mesos task. Is it a top level attribute in the "container" hash? E.g.
{code}
"container": {
"force": true,
...
}
{code}
?
> 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
>
> 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)
