[MESOS-1886] Allow docker pull on each run to be configurable

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 0.20.1
• Fix Version/s: 0.22.0
• Component/s: containerization
• Labels: docker
• Sprint: Mesosphere Q4 Sprint 2 - 11/14, Mesosphere Q4 Sprint 3 - 12/7
• Assignee: Timothy Chen
• Reporter: Chris Heller
• Shepherd: Benjamin Hindman
• Created: 09/Oct/14 12:17
• Updated: 02/Jul/15 18:43
• Resolved: 13/Apr/15 17:07

Description

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`.

Issue Links

• is related to: MESOS-1762 Avoid docker pull on each container run