Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker error running run_dev.sh #5

Closed
griz1112 opened this issue Nov 12, 2021 · 9 comments
Closed

Docker error running run_dev.sh #5

griz1112 opened this issue Nov 12, 2021 · 9 comments
Assignees

Comments

@griz1112
Copy link

Trying to build the dev env and when I run run_dev.sh I get this error message.
failed to create shim: OCI runtime create failed: container_linux.go:380: starting container process caused: error adding seccomp filter rule for syscall clone3: permission denied: unknown
~/gem_ws/src/isaac_ros_common
nvidia-docker is there nvidia-runtime is enabled. this is on a jetson xavier.

@hemalshahNV
Copy link
Contributor

The error seems to indicate an issue with the way Docker itself is setup or a mismatch with the nvidia-runtime perhaps. Could you check that you are running JetPack 4.6 by running the following: cat /etc/nv_tegra_release which should yield the following?

R32 (release), REVISION: 6.1, GCID: 27863751, BOARD: t186ref, EABI: aarch64, DATE: Mon Jul 26 19:36:31 UTC 2021

@hemalshahNV hemalshahNV self-assigned this Nov 12, 2021
@griz1112
Copy link
Author

Thats what it is. I'm on 5.2 will have to reflash thanks.

@griz1112
Copy link
Author

I reflashed it has the proper sdk now and the error is still there.

@hemalshahNV
Copy link
Contributor

You're right. This looks like an instance of related issue 1 and issue 2 with the NVIDIA Container Runtime and Docker version mismatch.

You can either downgrade Docker, use an experimental version of NVIDIA Container Runtime, or add flags --security-opt seccomp=unconfined to docker run command in run_dev.sh. We're evaluating the last option as a clean workaround in the meantime.

@griz1112
Copy link
Author

I was seeing something similar when I googled the error but the versions were higher than what is on the Xavier so I figured I was good since they were saying to downgrade to the version that is on the Xavier. I'll try again in a bit and let you know thanks.

@griz1112
Copy link
Author

Is this where I need to add the flag?

Run container from image

print_info "Running $CONTAINER_NAME"
docker run -it --rm --security-opt seccomp=unconfined
--privileged --network host
${DOCKER_ARGS[@]} \

Getting the same error when I do it this way.

@msrasheed
Copy link

msrasheed commented Dec 3, 2021

I had a similar issue and downgrading docker.io to 20.10.7-0ubuntu1~18.04.2 fixed the issue.
Got it to work after following the advice from this thread: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1950071
I used the archived version found here: http://jp.archive.ubuntu.com/ubuntu-ports/pool/universe/d/docker.io/

@swapnesh-wani-nvidia
Copy link

This has been fixed in the 1.7.0 version of nvidia-container-toolkit. Instruction on installing the nvidia-container-toolkit can be found here.

@hemalshahNV
Copy link
Contributor

@swapnesh-wani-nvidia That worked for me!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants