OCI rate limit

[ion-elgreco]

Name and Version

bitnami/mlflow

What steps will reproduce the bug?

Bitnami uses oci registry to host helm charts, this has a downside you will get a quick rate limited on docker:

 Error: Failed to render chart: exit status 1: Error: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/bitnamicharts/mlflow/manifests/sha256:a9fb6ade4f8b8f4d7e36a8bd45f174dd55f4d0818c246b91bfc99570cd923450: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

This is quite annoying since it requires you to download the chart for each version permanently.

What do you see instead?

Don't rate limit

[carrodher]

As announced in #30853, Bitnami charts hosted on DockerHub are subject to Docker's standard pull rate limits. To ensure uninterrupted access to up-to-date releases across all upstream-supported branches—without any limitations—you can upgrade to Bitnami Premium. Learn more here.

[ion-elgreco]

@carrodher ghcr doesn't have rate limits, why not use that?

[carrodher]

The choice of registry is a business decision, and for now, Bitnami charts will continue to be hosted on DockerHub. We understand that rate limits can be an inconvenience, which is why we offer Bitnami Premium as a solution for unlimited access to up-to-date releases across all supported branches.

[github-actions]

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

[github-actions]

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.

[xrow]

@carrodher

Hi,

can you explain why you have a copy of the bitnami images in other registries like quay.io, gcr.io, ... but pattern is not practical for charts?