[jira] [Commented] (MESOS-3505) Support specifying Docker image by Image ID.

["Guangya Liu (JIRA)" <ji...@apache.org>]

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

Guangya Liu commented on MESOS-3505:
------------------------------------

[~xujyan] two questions want to get your confirm, can you help?

1) 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.
>>>>> Did not quite catch what the problem here, why the task is using the image that it does not intended to use? Do you mean that the image might be updated in remote registry and the local cached one is still using the old one?

2) If support pulling docker images with digest and image ID, how end user get those digest and image ID before pull it?

> 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
>              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)