[
https://issues.apache.org/jira/browse/MESOS-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14165660#comment-14165660
]
Chris Heller edited comment on MESOS-1886 at 10/9/14 8:12 PM:
--------------------------------------------------------------
Making this only accessible in the DockerInfo message will limit the usefulness
of this. The selection is then on a per-framework basis, excepting when the
framework exposes the option to the user.
In my case, I'm running spark jobs inside docker images. With this design, in
order to change what behavior I want, I will need to rebuild spark!
This said, I am in agreement that overloading the meaning of the tag is a hack,
and your approach is better. Since I've already hacked spark to expose the
docker info, I can hack it again to set this flag.
But in the general case, a user needs access to the message, even if the
framework chose not to expose some of the options.
_Seems this is similar in theme to what I reported in MESOS-1860 :-)_
was (Author: chrisheller):
Making this only accessible in the DockerInfo message will limit the usefulness
of this. The selection is then on a per-framework basis, excepting when the
framework exposes the option to the user.
In my case, I'm running spark jobs inside docker images. With this design, in
order to change what behavior I want, I will need to rebuild spark!
_Seems this is similar in theme to what I reported in MESOS-1860 :-)_
The issue here is a variation on the issue I reported here: MESOS-1860, where
these options
> 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)
