-
Notifications
You must be signed in to change notification settings - Fork 158
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move to immutable identifiers #247
Comments
It would be nice if we could fast track this. Currently the sentence:
Isn't true, because we resolve the tag to the image id, then use that to create the slug. Removing this constraint means you can deploy any image that's in a docker registry, which is pretty awesome. |
I spiked into this a little on friday. Turns out, the immutable identifiers are not very useful and difficult to actually use. If you pull an image by tag, you have no way of telling what the identifier is after the fact. I think a better first step would be to just disable the resolving and caching for slugs. If I |
Gonna close this as a wontfix for now, mainly because |
I'm re-opening this, since it's now supported in ECS as of ~May: aws/amazon-ecs-agent#104 (comment) I think this is pretty important from a security perspective, since digests solve various attack vectors like mitm attacks, or credential exposure of your registry. |
This is a ways off, but something to keep on radar. Docker 1.6 will support immutable identifiers. See moby/moby#11109
The text was updated successfully, but these errors were encountered: