Unable to initiate jetson-inference container after update

Robotics & Edge Computing Jetson & Embedded Systems Jetson TX2
,
1

HI, i am having problem starting the jetson-inference container after update on my nano (Jetpack 4.5.1).

Logs as follows;

nano@nano:~/jetson-inference$ docker/run.sh
reading L4T version from /etc/nv_tegra_release
L4T BSP Version: L4T R32.5.2
size of data/networks: 2414907831 bytes
CONTAINER: nvcr.io/ea-linux4tegra/jetson-inference:r32.5.2
DATA_VOLUME: --volume /home/nano/jetson-inference/data:/jetson-inference/data --volume /home/nano/jetson-inference/python/training/classification/data:/jetson-inference/python/training/classification/data --volume /home/nano/jetson-inference/python/training/classification/models:/jetson-inference/python/training/classification/models --volume /home/nano/jetson-inference/python/training/detection/ssd/data:/jetson-inference/python/training/detection/ssd/data --volume /home/nano/jetson-inference/python/training/detection/ssd/models:/jetson-inference/python/training/detection/ssd/models
USER_VOLUME:
USER_COMMAND:
V4L2_DEVICES: --device /dev/video0
localuser:root being added to access control list
Unable to find image ‘nvcr.io/ea-linux4tegra/jetson-inference:r32.5.2’ locally
docker: Error response from daemon: unauthorized: authentication required.
See ‘docker run --help’.
nano@nano:~/jetson-inference$ sudo docker image ls
REPOSITORY TAG IMAGE ID CREATED SIZE
dustynv/jetson-inference r32.4.4 1bdd63ba4343 3 months ago 3.11GB
dustynv/jetson-inference r32.5.0 ccc2a5f19dad 9 months ago 2.89GB
nvcr.io/nvidia/dli/dli-nano-ai v2.0.1-r32.5.0 bc9051ff252d 11 months ago 3.73GB

It seems that after the update, the required L4T Version is R32.5.2.

Do i need to download a new container and if Yes, can you point provide me with the pull command to do this ?

Another strange this is that when i run JTOP on the terminal, the Jetpack version shown is now UNKNOWN. What is the possible reason for this to happen?

Benjamin

2

Hi @Benjamin_Lim, can you try running it like this?

docker/run.sh -c dustynv/jetson-inference:r32.5.0

I will also patch this in the docker/run.sh script so that it uses the right version of the container.

3

OK, this issue should be fixed by commit 4e1987 - thanks for letting me know.

Another strange this is that when i run JTOP on the terminal, the Jetpack version shown is now UNKNOWN. What is the possible reason for this to happen?

This is probably because JTOP also requires update for L4T R32.5.2 - I will let @rbonghi know.

4

Hi @dusty_nv , i tried running but still there is error

nano@nano:~/jetson-inference$ docker/run.sh -c dustynv/jetson-inference:r32.5.0
reading L4T version from /etc/nv_tegra_release
L4T BSP Version: L4T R32.5.2
[sudo] password for nano:
size of data/networks: 2414907831 bytes
CONTAINER: dustynv/jetson-inference:r32.5.0
DATA_VOLUME: --volume /home/nano/jetson-inference/data:/jetson-inference/data --volume /home/nano/jetson-inference/python/training/classification/data:/jetson-inference/python/training/classification/data --volume /home/nano/jetson-inference/python/training/classification/models:/jetson-inference/python/training/classification/models --volume /home/nano/jetson-inference/python/training/detection/ssd/data:/jetson-inference/python/training/detection/ssd/data --volume /home/nano/jetson-inference/python/training/detection/ssd/models:/jetson-inference/python/training/detection/ssd/models
USER_VOLUME:
USER_COMMAND:
V4L2_DEVICES: --device /dev/video0
localuser:root being added to access control list
docker: Error response from daemon: 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.

Not sure what causes this …

1 Like
5

HI @dusty_nv, have you got any further updates on how to resolve the container issue.

Thanks

6

Hi Benjamin!,

I work with docker and I had the same problem, the only way to resolve it was uninstall the docker (completely) and then reinstall it. I tried a lot of steps on forums but these did not work. At now, when a new uptdate is released, I preffer to update all system except the docker. I hope this could help you.

7

Hi @Benjamin_Lim, try updating or re-cloning your jetson-inference repo, because I had patched this issue by adding --security-opt seccomp=unconfined to this line of docker/run.sh:

https://github.com/dusty-nv/jetson-inference/blob/9b66fbf38dcd0e81f37eb3748db3df0a221b4fa7/docker/run.sh#L168

8

HI @dusty_nv . Thanks for your help.

I did not re-clone the repo though. Instead what i reckon was that editing the run.sh directly might also work and it did.

After that i tried to run

sudo docker/run.sh -c dustynv/jetson-inference:r32.5.0

and all is working again.

Thanks again. Cheers !

1 Like
9

Hi @cadiaz , thanks for your advice.

I found my solution through Dusty. Please refer to my reply to Dusty a while ago.

Thanks Anyway.

1 Like
10

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.