Any recommendation to avoid "Too many requests" limit with Python SDK #7040
Closed
skycaptain
started this conversation in
Ideas
Replies: 2 comments 3 replies
-
I realized I essentially answered my question in #6318: We could fork the python-sdk and configure the base image through dagger.json. |
Beta Was this translation helpful? Give feedback.
2 replies
-
The engine supports a mirrors setting. Have you tried that? Or doesn’t your Artifactory server work as a mirror? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We're currently considering using Dagger for production. As our main language is Python, we want to write our Dagger modules in Python. At the moment, we're using the default Python SDK that Dagger provides. This SDK fetches
python:3.11-slim
from Docker Hub.However, we've recently encountered the "Too Many Requests" limit on Docker Hub while trying to scale for production. We usually bypass this issue by proxying external images through our Artifactory server. The problem is, the image address appears to be hardcoded in the Python SDK. Therefore, we're seeking recommendations on how to properly scale this. Should we use a custom SDK and hard-code our proxied image? Given #6113, this doesn't seem to be an option for us at the moment, as we would be required to make parts about our infrastructure public.
For reference, see also #6486.
Beta Was this translation helpful? Give feedback.
All reactions