Could not resolve host: github.com
Its not possible to git clone in pods ?
Solution:Jump to solution
For anyone dealing with similar issues:
Try adding at least a 20 second sleep in your entrypoint (untested, but it might help).
However, what definitely works 100%: put everything needed directly into the Docker image (e.g. handle git clone and similar tasks during the Docker build, not at runtime). This way, everything just works....
19 Replies
i have my own docker img and locally it runs just fine, but in pod i get error
fatal: unable to access 'git URL': Could not resolve host: github.com
This shouldn't be happening, can you share your Pod ID?
I'll take a look.
@Nicolay
hello,
pod_id: qgp73qnibiesfy
it was terminated, but i can launch a new one
You should launch a new one, I'm taking down this machine for a little bit
i have just launch new one
gkveesj0dwx0l0
its now pulling docker img
still same error
I don't see the same error, can you try by doing something like
apt update?I can’t connect to the container because it didn’t pass the initial startup.
I’m getting this error:
Error response from daemon: Container 5f0fdf74f0dfdf82c0417d4272ceb8fa8f5362449321b9e5066dfec0d46c0b93 is not running
Connection to 100.65.21.83 closed.
Connection to ssh.runpod.io closed.
So unfortunately, I can’t run apt update or access the container at all.
error from system
start container for nicolay2145/comfy-wan-2.1:latest: begin
error starting sidecar: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: failed to cache mappings for userns: userns spawn: open userns path /proc/3936690/ns/user failed: No such file or directory: unknown
Try cloning into / or another directory you're certain exists at startup?
Also, if you have a pod open currently are you able to get to SSH?
The script fails specifically at the git clone step:
The container can't access GitHub during startup, so cloning always fails.
No, I'm not able to SSH into the pod at all.
The pod never fully starts, because it fails at the git clone step during initialization.
So I can't access the shell or do anything inside – it always crashes and restarts from the beginning.
Locally, the git clone step works every time – it's only on RunPod where the container can't reach GitHub.
Can you try making another Pod? I just simulated doing the same thing and I'm just fine :<
can i ask what region are you using ?
I just deleted the pod lol I can test it in EUR-IS-1 like you were on
😄
Are you using the official RunPod template for this? https://www.runpod.io/console/hub/runpod-workers/worker-comfyui
I checked the official RunPod ComfyUI worker. It doesn’t use git clone for ComfyUI at all, but relies on comfy-cli to do the installation (see the Dockerfile).
Is there a reason for this? Is comfy-cli whitelisted in your network, or are direct git clone requests restricted in some way?
There is no restriction or whitelist to our networking, I'm texting with a random PyTorch version but functionally all the pods are just docker containers with files in them anyway
Alright, I’ll try it the way it’s done in your official Dockerfile and see how it goes.
Thank you very much for your help! If I run into any other issues, I’ll open a ticket.
Solution
For anyone dealing with similar issues:
Try adding at least a 20 second sleep in your entrypoint (untested, but it might help).
However, what definitely works 100%: put everything needed directly into the Docker image (e.g. handle git clone and similar tasks during the Docker build, not at runtime). This way, everything just works.