-
Notifications
You must be signed in to change notification settings - Fork 41
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
Push a CNAB Bundle to GCR fails #69
Labels
bug
Something isn't working
Comments
From docker/app#562 |
I'm not sure #64 is a complete fix as I hit the problem when building at master (2770131). Here are steps to reproduce:
However, it works when pushing to docker hub. But, when I tried to copy the bundle from docker hub to GCR, I got the following error which may give a clue to the problem:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Pushing a CNAB bundle to
gcr.io
returns an error:After some investigation, we found multiple caveats:
null
layer field. This was fixed in Add a layer for the bundle config manifest #64 , adding a dummy layer pointing to the config object itself (it adds duplication)manifest list
, another an OCI index, and the CNAB itself be an OCI index too. This mix is not supported by gcr (and maybe other registries too). I think we can't guarantee that every service image will share the same format, so the minimum we can do is to fail if we detect a mix between images. That said, we need to also improve cnab-to-oci to detect which format we should use, depending the one found in the service images, instead of the fallback mechanism (try withOCI Index
thenDocker Manifest List
).The text was updated successfully, but these errors were encountered: