RunpodR
Runpod•11mo ago
nathank

Pod stuck trying to start custom docker image

Hi all I'm having trouble using a custom template. I'm trying to use a docker image provided by this simulation project https://github.com/Genesis-Embodied-AI/Genesis/blob/main/docker/Dockerfile and I built and uploaded the image to https://hub.docker.com/repository/docker/nathankau/genesis-docker/general

However when I create a template and use it to start a pod, it seems like the pod gets stuck trying to start the container. I have no container logs and the system logs repeat the following.

start container for docker.io/nathankau/genesis-docker:latest: begin

start container for docker.io/nathankau/genesis-docker:latest: begin

start container for docker.io/nathankau/genesis-docker:latest: begin

start container for docker.io/nathankau/genesis-docker:latest: begin

start container for docker.io/nathankau/genesis-docker:latest: begin

start container for docker.io/nathankau/genesis-docker:latest: begin


Perhaps my entry point ENTRYPOINT ["/bin/bash"] is wrong? I can start the docker locally just fine with
xhost +local:root # Allow the container to access the display

docker run --gpus all --rm -it \
-e DISPLAY=$DISPLAY \
-v /dev/dri:/dev/dri \
-v /tmp/.X11-unix/:/tmp/.X11-unix \
-v $PWD:/workspace \
genesis

Any help appreciated thanks!
Screenshot_2025-01-23_at_2.04.37_PM.png
GitHub
Genesis/docker/Dockerfile at main · Genesis-Embodied-AI/Genesis
A generative world for general-purpose robotics & embodied AI learning. - Genesis-Embodied-AI/Genesis
Solution
Yay I made it work. I unset both ENTRYPOINT and CMD in my Dockerfile so that the default nvidia_entrypoint.sh is used. Then in the runpod template UI, I set the container start command to sleep infinity.
Jump to solution
Was this page helpful?