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
Uniqueness of Checksums as Idenifiers #9
Comments
You're right, the IDs are too short. The UI shows a truncated ID to keep the output readable. The actual checksum is a SHA256 of the full content in tar archive. Going forward that's what we'll use as a canonical identifier. |
vieux
added a commit
that referenced
this issue
Jul 9, 2014
Update RELEASE-CHECKLIST with a few minor nits (periods, whitespace)
cpuguy83
pushed a commit
to cpuguy83/docker
that referenced
this issue
Oct 24, 2014
replace os/user with go-homedir
squaremo
added a commit
to squaremo/docker
that referenced
this issue
Apr 15, 2015
Net driver plugins
cherrry
pushed a commit
to cherrry/docker
that referenced
this issue
Feb 11, 2016
Revert "Return listenbuffer behavior"
thaJeztah
pushed a commit
to thaJeztah/docker
that referenced
this issue
Jul 8, 2022
containerd/pull: Use authorization
thaJeztah
added a commit
that referenced
this issue
Oct 18, 2022
[20.10] vendor moby/buildkit v0.8.3-31-gc0149372
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
How sure are you of that checksum's "universal uniqueness"?
That seems like a much shorter UUID than any other I've seen, and assuming that a faulty checksum uniquely identifies a container could lead to some terrible collisions.
The text was updated successfully, but these errors were encountered: