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
-
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?
-
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.
