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

Consider using OCI compliant media-types #621

Open
ChristianCiach opened this issue Dec 21, 2023 · 2 comments
Open

Consider using OCI compliant media-types #621

ChristianCiach opened this issue Dec 21, 2023 · 2 comments
Labels
discussion This issue is not a bug or feature and a conversation is needed to find an appropriate resolution enhancement This issue is a feature request

Comments

@ChristianCiach
Copy link

Describe the problem/challenge you have

I am trying to push Imgpkg artifacts to a Zot registry. Zot registry describes itself as a "vendor neutral" OCI registry. In practice this just means that Zot refuses to accept any image or artifact that uses a Docker (or any other non-OCI) specific mediaType.

For more information about this Zot's refusal to work with Docker artifacts, see this issue:

You can already see where I am going with this:

$ imgpkg push -i localhost:5000/test-bundle:v1.0.0 -f anyfile.txt --registry-insecure

imgpkg: Error: Writing 'localhost:5000/test-bundle:v1.0.0':
  Writing image:
    PUT http://localhost:5000/v2/test-bundle/manifests/v1.0.0:
      MANIFEST_INVALID: manifest invalid; map[description:During upload, manifests undergo several checks ensuring validity. If those checks fail, this error MAY be returned, unless a more specific error is included. The detail will contain information the failed validation. mediaType:application/vnd.docker.distribution.manifest.v2+json]

Describe the solution you'd like

Since it's probably unlikely for Zot to ever accept mediaTypes that are not defined by OCI, I would like imgpkg to (optionally) support the creation of bundles using standard OCI mediaTypes for its manifests and layers.


Vote on this request

This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.

👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"

We are also happy to receive and review Pull Requests if you want to help work on this issue.

@ChristianCiach ChristianCiach added carvel triage This issue has not yet been reviewed for validity enhancement This issue is a feature request labels Dec 21, 2023
@rchincha
Copy link

For more information about this Zot's refusal to work with Docker artifacts, see this issue:

Regardless of what the zot project does, I respectfully urge the carvel team to look at becoming OCI compliant.
For reference, helm already is: https://helm.sh/docs/topics/registries/

@praveenrewar
Copy link
Member

@ChristianCiach I believe you would be interested in this proposal.

@renuy renuy moved this to To Triage in Carvel Jan 2, 2024
@renuy renuy added discussion This issue is not a bug or feature and a conversation is needed to find an appropriate resolution and removed carvel triage This issue has not yet been reviewed for validity labels Jan 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion This issue is not a bug or feature and a conversation is needed to find an appropriate resolution enhancement This issue is a feature request
Projects
Status: To Triage
Development

No branches or pull requests

4 participants