Brandon Mitchell
Brandon Mitchell
If I were to guess, ECR may be rejecting the platform field on the config descriptor. I can see the value of it there, but traditionally the only descriptor that...
Cc @jlbutler that would know more about any ECR validation of the manifest.
I did a bit of testing to verify that it is indeed the platform field in the config descriptor that is triggering the ECR error. I think this is something...
If you wanted to test this yourself, you could recreate the manifest in the same ocidir without the platform field, and then copy that to ECR: ```shell cat mod.manifest
Word back from Docker experts are that this got added in v25 as part of https://github.com/moby/moby/pull/44598, and can be seen in the current code at https://github.com/moby/moby/blob/v26.0.0/image/tarexport/save.go#L237 @jlbutler what are your...
Docker has a PR to change their save output to no longer include this field: https://github.com/moby/moby/pull/47661
I'm going to close this here since it's not a bug in regclient, and it looks like Docker is likely to fix things on their side. In the mean time,...
The manifest output in `jsonPretty` is the original manifest, parsed into the known fields, and with whitespace to make it readable. You can see the specs for those manifests at:...
If you just want the digest, then `regctl image digest` or `regctl manifest head --require-digest` are the commands you want.
To resolve a platform, it has to pull the manifest list or index, which is why you typically don't want that flag in automation. You can run with `-v debug`...