Dennis K
How does runpod work with custom docker images? Multiple questions.
I have some questions:
1. If I use my own dockerhub image, does it have to pull the image from dockerhub everytime?
2. I tried to use a community template (ComfyUI - AI-Dock) and the pull from ghcr is very slow. This is related to the first question. Is there something that affects the pull speed? This sucks because I still get charged as I wait for my image to be downloaded. This image takes about 40mins to download ~5Gb while other take couple of mins for 5GB. So its not a problem on my end.
3. Are there any workarounds for pulling an image everytime? or bumping the pull speed? Can I request an add to cache for this image? I will be using it for now on.
4. How to use credentials registry? What do I set for password? My docker account pass or I generate a token with docker?
5. Is there anyway to reconstruct a runpod image? For example, I want to take "runpod/pytorch:2.2.1-py3.10-cuda12.1.1-devel-ubuntu22.04" and reconstruct it with slight modifications. Not use it as a base but reconstruct it.
Thank you.
17 replies
Ignore root start.sh and use custom persistent script.
Im trying to avoid using start.sh since I need to experiment with some different processes.
I've tried to copy the contents of start.sh and to point via the container start command to a install_req.sh script that is in the workspace folder. Im also unchecking "start jupyter notebook" and "ssh terminal access" since I don't want the container to run the original start.sh file. Maybe here Im confusing how these work or Im missing something.
The logs show that all is good but I can't use the runpod ui to start jupyter anymore and the actual ssh connection does not work anymore. Why is that happening although install_req.sh is the same as start.sh in the root dir?
Also , I've noticed that in the start.sh, there are some references to a pre_start.sh and a post_start.sh script in the root but I can't find them.
I don't want to get into messing with docker just now.
Thank you.
17 replies