Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    OCI support in Docker registry

    Scheduled Pinned Locked Moved Support
    docker-registryprogetoci
    2 Posts 2 Posters 37 Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • L Offline
      luminiscence_6236
      last edited by luminiscence_6236

      We are trying to upgrade to Helm v3, where one of new features is Docker OCI support. Briefly, command
      helm registry login docker.registry
      logs user into the docker registry (v2) and command
      helm chart push docker.registry/charts/chart:1.0
      pushes helm chart from local cache to remote registry. Still not absolutely seamless - at least, separate login command is required - but much better than before, when helm registry did not have local cache at all and had quite weird registry protocol.
      And what I've found after upgrading to Helm v3 is that ProGet Docker registry does not (completely) support OCI. I can login to the ProGet Docker registry with "helm registry login", but "helm chart push" command fails with 401 Unauthorized. I suspect the problem is somehow related to warnings
      WARN[0000] encountered unknown type application/tar+gzip; children may not be fetched
      WARN[0000] reference for unknown type: application/tar+gzip digest="sha256:983df72e9be8d2440e7c83ab3b2c1c8d3917f67c29fd9509cf00fd0b5940e3a5" mediatype=application/tar+gzip size=1209
      issued by ProGet during push. I've also tried to login via "docker login", with the same result.
      I understand that Helm 3 OCI support is experimental feature, but I was able to push the same chart to Azure container registry, so problem is most probably in ProGet Docker registry.
      Can you help me somehow? Are there any workarounds available?

      1 Reply Last reply Reply Quote 0
      • benB Offline
        ben inedo-engineer
        last edited by

        Hello @luminiscence_6236,

        It looks like ProGet is misinterpreting the auth token request helm sends during the second command as being anonymous. I've filed PG-1651 to address this.

        1 Reply Last reply Reply Quote 0

        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

        With your input, this post could be even better 💗

        Register Login
        • 1 / 1
        • First post
          Last post
        Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation