Skip to content
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

ggcr: creating an empty image index that contains empty image manifest not supported #1904

Open
codingben opened this issue Mar 21, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@codingben
Copy link

Describe the bug

We're using google/go-containerregistry in our tooling to create container images [1].

[1] https://github.com/kubevirt/containerdisks

Our steps:

  1. Create a new image manifest from empty image base that has DockerManifestSchema [1].
  2. Create a new image index from empty image index base that has OCIImageIndex [2].

When trying to copy it from internal registry to Quay container registry, it fails with an error that it's not supported.

[1] https://github.com/google/go-containerregistry/blob/main/pkg/v1/empty/image.go#L32
[2] https://github.com/google/go-containerregistry/blob/main/pkg/v1/empty/index.go#L32

To Reproduce

Just create an empty image index with empty image inside and try to copy it from internal registry to external container registry.

Expected behavior

Empty image manifest and empty image index should have the same media type. Ideally only and just OCI and not Docker.

@codingben codingben added the bug Something isn't working label Mar 21, 2024
@codingben codingben changed the title ggcr: creating an empty image index from empty image manifest not supported ggcr: creating an empty image index that contains empty image manifest not supported Mar 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant