jetson-inference: Docker fails after reboot.

I did a clean install of JetPack 6.0DP on my Jetson Orin Nano. Onto a 500 Gb NVMe drive. All good and eveything installed. Then installed jetson-inference and jetson-containers from this site. Everything runs perfectly. Tested almost all examples in inference and all good.

The I rebooted my Jetson. Now docker fails to run. If I run sudo systemctl status docker

It just says it failed to load. No real error message beyond docker.service: Failed with result 'error code'. Process is ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE

Any ideas?

About this issue

Original URL
State: open
Created 4 months ago
Comments: 22 (7 by maintainers)

Most upvoted comments

I just tried this and it worked for me. Someone posted it in the Nvidia forum thread mentioned above sudo update-alternatives --set iptables /usr/sbin/iptables-legacy sudo apt reinstall docker-ce

AZSupra on Mar 1, 2024

You can find links to my OpenCV+CUDA binaries here - they are tarballs of opencv deb’s that get installed in the containers by opencv_install.sh

https://github.com/dusty-nv/jetson-containers/blob/d8992335108db11b4e003db0d4cf03cf2a1cb5b6/packages/opencv/config.py#L25

Sorry, if you can’t fix what the upgrade did to docker, then yea I would re-flash one more time and then not upgrade it until issue is resolved or you know what packages to pin.

Figured out how to do this. Ubuntu is still fairly new to me. Found your gz files and the DEB name from the link you gave above Then ran :

sudo ./jetson-containers/packages/opencv/opencv_install.sh https://nvidia.box.com/shared/static/ngp26xb9hb7dqbu6pbs7cs9flztmqwg0.gz OpenCV-4.8.1-aarch64.tar.gz

Worked a treat and now I have openCV 4.8.1 installed in the base environment with CUDA support

Thanks Dusty!

smbunn on Mar 2, 2024

@smbunn We ran into this same issue on our AGX Orin running Jetpack 6. I’m not sure what we did differently, but we ran the exact commands mentioned in the post you linked above (where we ran the commands specified in the issue they link to first) and that seemed to do the trick. We are now able to run the image using the run_dev.sh script.

nlitz88 on Feb 27, 2024

I looked at run.sh and it has --network host which to me seems like it never uses the bridge docker0. But docker itself cannot start up and fails on the bridge connection. I have tried the repair indicated in the nvidia developers forum, but like many others have had to report that this does not work. So at present I maintain a clean 'just installed" image of my Jetson Orin Nano with JetPack 6.0 and try and make sure no updates ever occur. This gets tricky as some installs want you to run update and upgrade. Hopefully someone will figure out how to repair the bridge in Docker so we can resume normal Ubuntu updates processes. When I accidentally allow a script to run that updates, I clone my NVMe drive back to the original and start again. I have now done this so often I keep 2 NVMe drives on the go so I can always swap to the clean one when docker fails.

I will add that this is still worthwhile as the dusty-nv containers are awesome! I am really enjoying using them.

smbunn on Feb 27, 2024