-
Notifications
You must be signed in to change notification settings - Fork 525
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
runpod docker credentials not working when using image_id from private repository #4269
Comments
also unrelated but it would be nice to be able to specify multiple cloud providers in the yaml |
This is supported; check out https://skypilot.readthedocs.io/en/latest/examples/auto-failover.html#multiple-candidate-resources. |
Got it, thanks. Any idea about the docker credentials? |
It can be an issue with our pumping for the docker credentials for RunPod specifically. cc'ing @cblmemo for a look. |
Yes, this is due to we directly setting the image id to create pod instead of using the DockerInitializer. A solution would be manually calling the runpod credential API if env variables is detected. Will submit a PR to fix this. |
Because runpod doesn't support docker I need to use my docker image as the base image_id but setting the
SKYPILOT_DOCKER_USERNAME
andSKYPILOT_DOCKER_PASSWORD
doesn't allow the created runpod to have access to the private repo. However, if you manually change the dockerhub config on the runpod web UI (which I setup beforehand) it works fine. Is there a way to authenticate the docker image for the created pod automatically?For reference here's my config:
and then an image of the runpod UI that I'm referring to:
Version & Commit info:
sky -v
: skypilot, version 0.7.0sky -c
: 3f62588The text was updated successfully, but these errors were encountered: