[
https://issues.apache.org/jira/browse/MESOS-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14325275#comment-14325275
]
Henning Schmiedehausen commented on MESOS-2364:
-----------------------------------------------
(This is a backport from our internal, 0.21.0 based version of Apache Mesos
where no force flag existed. Even if it had existed, it does not do what we
want it to do).
Given that this flag does not exist in 0.21.0 and not exist in 0.21.1, there is
no support by any framework for them (except the ones that happen to be
maintained by the same people that also commit to mesos).
As we do not plan to ever use chronos or marathon, this implies that we will
have to write support code all throughout the stack (which for us has more than
just a framework but also orchestration and coordination components) *or* we
change the behavior of mesos to be in line with other popular tools (such as
Maven), that our developers understand and know how to use.
Making a call on this was straightforward for me. :-)
> Docker containerizer should pull every time if image tag is ":latest"
> ---------------------------------------------------------------------
>
> Key: MESOS-2364
> URL: https://issues.apache.org/jira/browse/MESOS-2364
> Project: Mesos
> Issue Type: Improvement
> Components: docker
> Affects Versions: 0.20.1, 0.21.1
> Reporter: Henning Schmiedehausen
> Assignee: Henning Schmiedehausen
> Priority: Minor
>
> The "latest" tag for a docker image denominates the newest or most recent
> version of a docker image. So the docker containerizer should pull every time
> from the registry if the "latest" tag is encountered to ensure that the most
> recent version is used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
