search

NVIDIA / enroot

A simple yet powerful tool to turn traditional container/OS images into unprivileged sandboxes.
Apache License 2.0
610 stars 93 forks source link

Enroot fails to launch server omniverse container that a client can connect with, podman works #103

Closed mjlbach closed 2 years ago

mjlbach commented 2 years ago

I'm sorry this bug report is a bit complicated (and I didn't know how to phrase it). We use enroot on our cluster, and one issue has popped up trying to use Nvidia's omniverse using the remote kit viewer when the server host is using enroot. Launching the same container via podman does not have the issue (podman and enroot both work for the client container). I've reproduced the issue with instructions below. Note, my build instructions assume you are able to build the container with podman, and have nvidia-container-toolkit installed.

https://github.com/mjlbach/enroot-isaac-issue

mjlbach commented 2 years ago

Ah sorry, it seems like I'm misunderstanding how to override the default entrypoint in enroot.

The correct invocation would be:

export ENROOT_MOUNT_HOME=y NVIDIA_DRIVER_CAPABILITIES=all
enroot start --rw --root -e ACCEPT_EULA=y -e DISPLAY -e NVIDIA_DRIVER_CAPABILITIES \
    --rc <(echo /isaac-sim/runheadless.webrtc.sh) nvidia+isaac-sim+2021.1.1