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: beginstart container for docker.io/nathankau/genesis-docker:latest: beginstart container for docker.io/nathankau/genesis-docker:latest: beginstart container for docker.io/nathankau/genesis-docker:latest: beginstart container for docker.io/nathankau/genesis-docker:latest: beginstart container for docker.io/nathankau/genesis-docker:latest: begin
start container for docker.io/nathankau/genesis-docker:latest: beginstart container for docker.io/nathankau/genesis-docker:latest: beginstart container for docker.io/nathankau/genesis-docker:latest: beginstart container for docker.io/nathankau/genesis-docker:latest: beginstart container for docker.io/nathankau/genesis-docker:latest: beginstart container for docker.io/nathankau/genesis-docker:latest: begin
Perhaps my entry point
ENTRYPOINT ["/bin/bash"]
ENTRYPOINT ["/bin/bash"]
is wrong? I can start the docker locally just fine with
xhost +local:root # Allow the container to access the displaydocker run --gpus all --rm -it \-e DISPLAY=$DISPLAY \-v /dev/dri:/dev/dri \-v /tmp/.X11-unix/:/tmp/.X11-unix \-v $PWD:/workspace \genesis
xhost +local:root # Allow the container to access the displaydocker run --gpus all --rm -it \-e DISPLAY=$DISPLAY \-v /dev/dri:/dev/dri \-v /tmp/.X11-unix/:/tmp/.X11-unix \-v $PWD:/workspace \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