Originally we don't want to always pull with latest as that's what docker run does as well which skips pull if the image exists, and has different issues involved with this.
However with MESOS-1886 we can make this optional, just figuring out where this configuration should be, at the latest discussions is leaning towards DockerInfo which is a per task level. Tim On Mon, Oct 27, 2014 at 10:19 AM, Ankur Chauhan <[email protected]> wrote: > I had a similar issue and what I ended up doing was to explicitly set the > version tag instead of just saying :latest. That makes the whole system > much more stable/predictable. For the cost of a single curl call when you > push is much better for debugging issues and the state of the system. > -- Ankur > > On 27 Oct 2014, at 09:58, Donald Laidlaw <[email protected]> wrote: > > I have Mesos 0.20.1 and Marathon 0.7.3 > > When marathon is creating a new App, and asks Mesos to start an instance, > what docker command is run by mesos? > > The reason I ask is that I am referencing a docker container without a > tag, expecting the tag "latest" to be used. And that seems to work. But > when I update the container with a new version, and set the "latest" tag to > point to the new version in the docker registry, mesos does not pull down > that new version. I suspect mesos is checking to see if there is an image > of the same name already on the slave and not issuing a pull request in > that case. > > Thanks, > Don > > > >
