-
Notifications
You must be signed in to change notification settings - Fork 1
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
Handle custom containers #42
Labels
Comments
I think this is handled, right? Isn't this what we did for the LBNL use case? |
It's handled locally but not if deployed on a K8s cluster. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, custom containers (one's that are uploaded to django directly) aren't handled, only containers stored on dockerhub are. IMO the way to handle this is to use Amazon ECR to store these custom containers. Then the Kubernetes Job would specify that the image should be pulled from this repo, instead of dockerhub. Here are some kubernetes docs regarding this.
The text was updated successfully, but these errors were encountered: