Dennis K
How does runpod work with custom docker images? Multiple questions.
Is it the same way? Using a base image doesn't stack all the previous layers from the base image and locks me out from modifying those layers? allowing me only to add new layers on top? Im still a beginner with docker
17 replies
How does runpod work with custom docker images? Multiple questions.
@digigoblin @nerdylive By reconstructing it I mean actually reconstructing it using another image as reference.
Maybe this process its called something else but here's what I did in this direction:
1. Find a reference image (runpod/pytorch:2.2.1-py3.10-cuda12.1.1-devel-ubuntu22.04)
2. Analyze the image layers from dockerhub or with dockerdesktop.
3. Copy paste all layers info and their respective commands in an excel
4. Gave the excel to chatgpt and request a dockerfile based on that excel
5. Chatgpt gave me a new dockerfile for a new image that is somewhat a replica of my reference image. Im not sure how accurate it is but it worked.
6. Reconstruct the reference image + my modifications
I was wondering if there is a more straight forward way of doing this.
17 replies
Ignore root start.sh and use custom persistent script.
There are no env variables on the starting command. Don't they populate automatically from the start.sh script? Or these are related to the ssh terminal access and start jupyter notebook checkboxes? If so, does it mean I can't bypas in anyway the start.sh at the root? The final goal would be to add some commands right before # Start jupyter lab code is exectued in the start.sh. But since start.sh is not persistent I created this install_req.sh in the workspace volume
17 replies
Ignore root start.sh and use custom persistent script.
Yea, sorry. Im using https://hub.docker.com/layers/runpod/pytorch/2.1.0-py3.10-cuda11.8.0-devel-ubuntu22.04/images/sha256-2594f25beeef751aeebcc207ba4c45a382ba174655f01e15cbbfad0e2bdb5ef8?context=explore
17 replies