New Jetson Orin Nano - Docker Issue

Robotics & Edge Computing Jetson Systems Jetson Orin Nano
1

Hi all,

I just bought my Jetson Orin Nano and I am actually very new to this and Linux (I am actually a Windows guy) as well.

I am into my 5th day of configuring this Jetson and I am still not able to get past this issue, thus hoping to get some help from this forum.

I am using this Jetson AI Lab guide (🚀 Initial Setup Guide - Jetson Orin Nano - NVIDIA Jetson AI Lab) to flash my unit to 5.1.3, then subsequently to 6.2

Now I can never get past this guide (🔖 SSD + Docker - NVIDIA Jetson AI Lab) where I get to setup the docker to the SSD.

The error message I always face is as below:
sudo systemctl restart docker
sudo usermod -aG docker $USER
newgrp docker
Job for docker.service failed because the control process exited with error code.
See “systemctl status docker.service” and “journalctl -xeu docker.service” for details.

When I run systemctl status docker.service, the following is the message:
× docker.service - Docker Application Container Engine

  • Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)*

  • Active: failed (Result: exit-code) since Sat 2025-02-22 00:48:56 +08; 35s ago*

TriggeredBy: × docker.socket

  •   Docs: https://docs.docker.com*
  • Process: 8151 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)*
  • Main PID: 8151 (code=exited, status=1/FAILURE)*
  •    CPU: 140ms*

Feb 22 00:48:56 blitz-jetson systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Feb 22 00:48:56 blitz-jetson systemd[1]: Stopped Docker Application Container Engine.
Feb 22 00:48:56 blitz-jetson systemd[1]: docker.service: Start request repeated too quickly.
Feb 22 00:48:56 blitz-jetson systemd[1]: docker.service: Failed with result ‘exit-code’.
Feb 22 00:48:56 blitz-jetson systemd[1]: Failed to start Docker Application Container Engine.

IS there anyway I can resolve this or my Jetson set is actually faulty?

Really feeling hopeless now, will appreciate any help to resolve so I can get going to use the set.

Thanks!

2

I gave it one final try by reflashing my SD card to the 6.2 image again.

This round what I did was after the initial setup pages after the system bootup, I did not allow the system to upgrade Ubuntu and the rest of the software when it prompts.

From there, I was able to install the dusty jet containers, ollama and even the open-web UI as per the Jetson ai labs page without any issue and docker was running fine.

However! After I find that everything is running fine, I let the system to upgrade itself and all of the software and voila, the above problem happens again with the daemon and docker unable to run anymore (same error as my previous post). Does it means I forever cannot upgrade my Jetson’s software?

Is this even normal in the 1st place for the Jetson series?

Will Appreciate any help as I am really at my wit’s end after trying and searching so much for help.

3

Docker issue.

You need to downgrade. This is what I downgraded:

sudo apt install docker-ce=5:27.5.1-1~ubuntu.22.04~jammy \
                 docker-ce-cli=5:27.5.1-1~ubuntu.22.04~jammy \
                 docker-compose-plugin=2.32.4-1~ubuntu.22.04~jammy \
                 docker-buildx-plugin=0.20.0-1~ubuntu.22.04~jammy \
                 docker-ce-rootless-extras=5:27.5.1-1~ubuntu.22.04~jammy

However, I’m seeing that you might only need to downgrade the following:

sudo apt install docker-ce=5:27.5.1-1~ubuntu.22.04~jammy \
                 docker-ce-cli=5:27.5.1-1~ubuntu.22.04~jammy

and then mark them, so you don’t upgrade them:


sudo apt-mark hold docker-ce=5:27.5.1-1~ubuntu.22.04~jammy
sudo apt-mark hold docker-ce-cli=5:27.5.1-1~ubuntu.22.04~jammy
4

Thanks for the help!!! Really appreciate the marking command.
Just need to ask as I am new to Linux, thus I am usingthe GUI a lot.

  1. By using the marking command, will the Software Update at the Linux GUI still update the docker?
  2. Can I stay 27.5.1 forever or in future there is a need to upgrade the version? Is this a normal trend for Jetsons?
    Thanks again!!
5

I’ve been playing with this thing for a week.
I’m both impressed and frustrated in equal parts, lol. Been a bit of a learning curve.

To answer your second question; ubuntu will keep those at that level until you apt unhold them. Obviously, at some point they will be significantly out of date.

At some point, I assume this will be fixed. The solution is a jetson kernel-level issue, so I’m assuming this will be a Jetpack 6.3+ level fix.

Unless the SDK manager forces a specific version, I think this hold will remain in effect, even if you do an apt upgrade

6

Thank you!
Yeah I share the same sentiments as you, was initially impressed by such a little thing but powerful… but the docker issue (which I spend almost a week every since purchase) frustated me.

As a pure Windows guy, I think this will be a very steep learning but fun curve for me, I hope :)

7

I would suggest using an SSD, and making backups of it using a USB caddy, and partition it sensibly, so user files, models, etc are on a different partition. That way when you break it in new and interesting ways, you can backtrack.

docker is also hungry for space, so you’ll find you run out pretty quickly.

Ask me how many times I’ve reflashed this thing in the last week… lol.

8

haha seeing how many reflashes which I have done for the past week as I dunno the solution, I cannot imagine how many reflashes you went through? 6 to 7 times?

I am following this guide to migrate from SD card to SSD:

Hope this is the correct way… :)

9

I’ve updated to Jetpack 6.2 and get the same issues after having run nicely before.
I’ve reflashed everything and get the same errors. I’ve tried the official docker install script: same errors. It must be caused by docker v28. Earlier versions worked for me, but i cannot get GPU support running in docker any longer. I’ll have to reflash to an earlier Jetpack.

I can’t seem to find a solution, so I’ll just downgrade and try it again in a few weeks.

10

Pardon my ignorance but how do you check for GPU support?

11

I’m starting docker with nvidia runtime but it does not result in GPU usage. jtop shows 100% CPU, GPU remains at 0%. This has not happened with my latest setup.

13

Hi, all

As discussed above, this issue is caused by the latest docker (released last week) requires some extra kernel configuration.
Our internal team is working on this issue actively.

For now, please downgrade the docker to 27.5.1 or build a custom kernel manually.
Please find below for more info:

Thanks.