When running python simple/time_stepping.py, the following error is raised: [Warning] [omni.kit.app.plugin] --carb/app/extensions/folders2/0=“/isaac-sim/_build/target-deps/kit_sdk_release/_build/linux-x86_64/release/exts”: prefix ‘–carb/’ is deprecated. Override should be --/app/extensions/folders2/0=“/isaac-sim/_build/target-deps/kit_sdk_release/_build/linux-x86_64/release/exts” [Warning] [omni.kit.app.plugin] --carb/app/extensions/folders2/1=“/isaac-sim/_build/target-deps/kit_sdk_release/_build/linux-x86_64/release/extsPhysics”: prefix ‘–carb/’ is deprecated. Override should be --/app/extensions/folders2/1=“/isaac-sim/_build/target-deps/kit_sdk_release/_build/linux-x86_64/release/extsPhysics” [Warning] [omni.kit.app.plugin] --carb/app/extensions/folders2/2=“/isaac-sim/_build/linux-x86_64/release/exts”: prefix ‘–carb/’ is deprecated. Override should be --/app/extensions/folders2/2=“/isaac-sim/_build/linux-x86_64/release/exts” Omniverse Kit cannot be run as the root user without the --allow-root flag. Running as root should not be necessary under most circumstances. Doing this may cause kit to encounter errors when running as a normal user again. Segmentation fault (core dumped)
Running in docker, followed all previous steps about conda env setup.
Have anyone encountered something similar before?
Hi, the --allow-root is needed when running Isaac Sim in a container. This flag has already been added to the runheadless.sh file in the /isaac-sim folder of the container.
Thank you for your input, @Sheikh_Dawood. But I am a bit confused about running it headlessly.
The way I am running the container is through the command: sudo docker run --entrypoint ./runapp.sh --gpus all -e “ACCEPT_EULA=Y” --rm -v /tmp/.X11-unix:/tmp/.X11-unix -v /etc/localtime:/etc/localtime:ro -e DISPLAY=unix${DISPLAY} --network=host nvcr.io/nvidia/isaac-sim:2020.2.2_ea
Then it runs the Omniverse Kit window and starts the container. I am connecting to the docker container then with the VS code and executing the commands from the samples tutorial.
Is there another way to run the docker, such that it has –allow-root flag enabled?
met the same issue when executing another python sample about changing resolution.
this workaround helps. but why this could cause an error? Normally when people start a container, they always use root user to execute the commands. It’s not convenient to edit every exts file to add the allow-root arg
You can always edit the python_app.py file (/isaac-sim/exts/omni.isaac.python_app/omni/isaac/python_app/python_app.py) and set --allow-root to True once.