[
https://issues.apache.org/jira/browse/MESOS-7089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Pronin updated MESOS-7089:
-------------------------------
Description: Docker’s mutable tags serve as a layer of indirection which
can be used to point a tag to different images digests (concrete immutable
images) at different points in time. For instance `latest` tag can point
`digest-0` at t0 and then to `digest-1` at t1. Mesos has support for local
docker registry, where the images are files on the local filesystem, named
either as `repo:tag` or `repo@digest`. This approach trims the degree of
freedom provided by the indirection mentioned above (from Docker’s mutable
tags), which can be essential in some cases. For instance, it might be useful
in cases, where the operator of a cluster would like to rollout image updates
without having the customers to update their task configuration. (was:
Docker’s mutable tags serve as a layer of indirection which can be used to
point a tag to different images digests (concrete immutable images) at
different points in time. For instance `latest` tag can point `digest-0` at t0
and then to `digest-1` at t1. Mesos has support for local docker registry,
where the images are files on the local filesystem, named either as `repo:tag`
or `repo:digest`. This approach trims the degree of freedom provided by the
indirection mentioned above (from Docker’s mutable tags), which can be
essential in some cases. For instance, it might be useful in cases, where the
operator of a cluster would like to rollout image updates without having the
customers to update their task configuration.)
> Local Docker Resolver for Mesos Containerizer
> ---------------------------------------------
>
> Key: MESOS-7089
> URL: https://issues.apache.org/jira/browse/MESOS-7089
> Project: Mesos
> Issue Type: Story
> Reporter: Santhosh Kumar Shanmugham
>
> Docker’s mutable tags serve as a layer of indirection which can be used to
> point a tag to different images digests (concrete immutable images) at
> different points in time. For instance `latest` tag can point `digest-0` at
> t0 and then to `digest-1` at t1. Mesos has support for local docker registry,
> where the images are files on the local filesystem, named either as
> `repo:tag` or `repo@digest`. This approach trims the degree of freedom
> provided by the indirection mentioned above (from Docker’s mutable tags),
> which can be essential in some cases. For instance, it might be useful in
> cases, where the operator of a cluster would like to rollout image updates
> without having the customers to update their task configuration.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
