[
https://issues.apache.org/jira/browse/AURORA-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14643630#comment-14643630
]
brian wickman commented on AURORA-1014:
---------------------------------------
This is possible with docker >= 1.6 but only if you're using registry v2.
Interestingly even then you can't really pull by id. You can resolve a tag to
id, but then you must query the metadata to find the sha256 digest, then pull
via "repo@sha256:<digest>". The latter operation is only supported by the v2
registry which is not yet fully implemented afaict.
> Client binding_helper to resolve docker label to a stable ID at create
> ----------------------------------------------------------------------
>
> Key: AURORA-1014
> URL: https://issues.apache.org/jira/browse/AURORA-1014
> Project: Aurora
> Issue Type: Bug
> Components: Client, Packaging
> Reporter: Kevin Sweeney
> Assignee: brian wickman
>
> Follow-up from discussion on IRC:
> Some docker labels are mutable, meaning the image a task runs in could change
> from restart to restart even if the rest of the task config doesn't change.
> This breaks assumptions that make rolling updates the safe and preferred way
> to deploy a new Aurora job
> Add a binding helper that resolves a docker label to an immutable image
> identifier at create time and make it the default for the Docker helper
> introduced in https://reviews.apache.org/r/28920/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
