-
Notifications
You must be signed in to change notification settings - Fork 384
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
Replace docker.io as the default registry with <local> #448
Conversation
@baude @TomSweeneyRedHat @mheon @runcom @mtrmac WDYT This would change the default for |
@nalind WDYT |
|
Sure I would be fine with image:latest as well. but the code is putting a "/" in in that case and gets an invalid name. |
Signed-off-by: Daniel J Walsh <[email protected]>
@runcom Do you know why git is failing? |
Is there a reason it is |
@mheon Just this is the way the it worked in docker.io. |
@rhatdan I'm just worried about |
@mheon I would say lets get this in first and then we can look at that. |
FWIW the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As discussed yesterday, allowing this kind of input for containers-storage:
may well make sense.
Wholesale redefining the meaning of existing strings without considering each individual string <-> c/image/docker/reference.*
conversion is not really practical.
{"//busybox", "docker.io/library/busybox:latest"}, // Default tag | ||
{"//busybox:notlatest", "<local>/library/busybox:notlatest"}, // Explicit tag | ||
{"//busybox" + sha256digest, "<local>/library/busybox" + sha256digest}, // Explicit digest | ||
{"//busybox", "<local>/library/busybox:latest"}, // Default tag |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This still essentially breaks the world; skopeo inspect docker://busybox
will no longer do anything useful.
{"busybox:latest", "", "docker.io/library/busybox:latest"}, // Explicit tag | ||
{"busybox@" + sha256digest, "", "docker.io/library/busybox@" + sha256digest}, // Explicit digest | ||
{"busybox:latest", "", "<local>/library/busybox:latest"}, // Explicit tag | ||
{"busybox@" + sha256digest, "", "<local>/library/busybox@" + sha256digest}, // Explicit digest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See the long comment in docker/tarfile/Destination.PutManifest
, this would break interoperability with projectatomic/docker.
@@ -136,7 +136,7 @@ var prmExactMatchTestTable = []prmSymmetricTableTest{ | |||
{"busybox" + digestSuffix, "busybox" + digestSuffix, true}, // NOTE: This is not documented; signing digests is not recommended at this time. | |||
// Non-canonical reference format is canonicalized | |||
{"library/busybox:latest", "busybox:latest", true}, | |||
{"docker.io/library/busybox:latest", "busybox:latest", true}, | |||
{"<local>/library/busybox:latest", "busybox:latest", true}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This redefines the meaning of existing signatures, e.g. https://rhelblog.redhat.com/2016/07/22/container-image-signing/ shows a reference that does not contain a host name.
(Recent code uses the fully explicit format in created signatures, I’m afraid that hasn’t been originally the case.)
i.e. basically replace the That could be simpler to do on top of #426, which eliminates a fair amount of redundancy in the |
Can we get #426 merged? |
CLosing this PR in favor of containers/buildah#648 |
Signed-off-by: Daniel J Walsh [email protected]