mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jie Yu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-3505) Support specifying Docker image by Image ID.
Date Tue, 17 Jan 2017 14:24:26 GMT

    [ https://issues.apache.org/jira/browse/MESOS-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15826118#comment-15826118
] 

Jie Yu commented on MESOS-3505:
-------------------------------

commit 92595f4f120e48c98b48add4a58548cba7745312
Author: Ilya Pronin <ipronin@twopensource.com>
Date:   Tue Jan 17 14:33:00 2017 +0100

    Added support for pulling Docker images by digest.

    For now we can only use digests to pull images that were pushed with
    Docker 1.9 and older or from Registry 2.2.1 and older. Newer versions
    use Schema 2 manifests that are not converted by the registry when
    pulling by digest.

    Review: https://reviews.apache.org/r/53848/

> Support specifying Docker image by Image ID.
> --------------------------------------------
>
>                 Key: MESOS-3505
>                 URL: https://issues.apache.org/jira/browse/MESOS-3505
>             Project: Mesos
>          Issue Type: Story
>            Reporter: Yan Xu
>            Assignee: Ilya Pronin
>              Labels: mesosphere
>
> A common way to specify a Docker image with the docker engine is through {{repo:tag}},
which is convenient and sufficient for most people in most scenarios. However this combination
is neither precise nor immutable.
> For this reason, it's possible when an image with a {{repo:tag}} already cached locally
on an agent host and a task requiring this {{repo:tag}} arrives, it's using an image that's
different than the one the user intended.
> Docker CLI already supports referring to an image by {{repo@id}}, where the ID can have
two forms:
> * v1 Image ID
> * digest
> Native Mesos provisioner should support the same for Docker images. IMO it's fine if
image discovery by ID is not supported (and thus still requiring {{repo:tag}} to be specified)
(looks like [v2 registry|http://docs.docker.com/registry/spec/api/] does support it) but the
user can optionally specify an image ID and match it against the cached / newly pulled image.
If the ID doesn't match the cached image, the store can re-pull it; if the ID doesn't match
the newly pulled image (manifest), the provisioner can fail the request without having the
user unknowingly running its task on the wrong image.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message