Docker Hub OCI registry for helm charts is unstable and returns 401 errors

Bitnami developer here. We have our helm charts in Docker Hub using OCI, and we’re having several users with stability issues, getting errors like this:

Error: could not download oci://registry-1.docker.io/bitnamicharts/common: failed to authorize: failed to fetch anonymous token: unexpected status from GET request to https://auth.docker.io/token?scope=repository%3Abitnamicharts%2Fcommon%3Apull&service=registry.docker.io: 401 Unauthorized
helm.go:84: [debug] failed to authorize: failed to fetch anonymous token: unexpected status from GET request to https://auth.docker.io/token?scope=repository%3Abitnamicharts%2Fcommon%3Apull&service=registry.docker.io: 401 Unauthorized
could not download oci://registry-1.docker.io/bitnamicharts/common
helm.sh/helm/v3/pkg/downloader.(*Manager).downloadAll
	helm.sh/helm/v3/pkg/downloader/manager.go:356
helm.sh/helm/v3/pkg/downloader.(*Manager).Update
	helm.sh/helm/v3/pkg/downloader/manager.go:200
main.newDependencyUpdateCmd.func1
	helm.sh/helm/v3/cmd/helm/dependency_update.go:74
github.com/spf13/cobra.(*Command).execute
	github.com/spf13/cobra@v1.7.0/command.go:940
github.com/spf13/cobra.(*Command).ExecuteC
	github.com/spf13/cobra@v1.7.0/command.go:1068
github.com/spf13/cobra.(*Command).Execute
	github.com/spf13/cobra@v1.7.0/command.go:992
main.main
	helm.sh/helm/v3/cmd/helm/helm.go:83
runtime.main
	runtime/proc.go:250
runtime.goexit
	runtime/asm_amd64.s:1598

Is there any solution to avoid these issues when using OCI?

Source: [bitnami/multus-cni] The registry-1.docker.io registry isn’t working. Update documentation to use the correct registry. · Issue #19599 · bitnami/charts (github.com)

I could reproduce the issue. I don’t know why it requires logging in to run helm install, but it worked only when I logged in to Docker Hub. Would you report the issue on the Hub Feedback?

Or as a verified publisher with many useful content, you could probably speed up the process by contacting Docker Support as well.

https://hub.docker.com/support/contact/

For future readers: it seems that the bug is not in Docker Hub, but helm itself:

https://github.com/bitnami/charts/issues/19599#issuecomment-1757245886