AGX Orin 64 GB - JetPack 6.2 Docker Issue after Flashing the Board

Robotics & Edge Computing Jetson & Embedded Systems Jetson AGX Orin
1

I recently flashed my NVIDIA AGX Orin Dev board with JetPack 6.2 and the installation failed. Specifically, NVIDIA Container Runtime with Docker integration is failing.

By SSH to the board after flashing I got the following:

systemctl status docker.service
× docker.service - Docker Application Container Engine
     Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Tue 2025-02-25 18:59:26 EST; 31min ago
TriggeredBy: × docker.socket
       Docs: https://docs.docker.com
    Process: 53010 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
   Main PID: 53010 (code=exited, status=1/FAILURE)
        CPU: 135ms

Feb 25 18:59:26 ubuntu systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Feb 25 18:59:26 ubuntu systemd[1]: Stopped Docker Application Container Engine.
Feb 25 18:59:26 ubuntu systemd[1]: docker.service: Start request repeated too quickly.
Feb 25 18:59:26 ubuntu systemd[1]: docker.service: Failed with result 'exit-code'.
Feb 25 18:59:26 ubuntu systemd[1]: Failed to start Docker Application Container Engine.

and

sudo systemctl restart 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.

I don’t know how to fix this, and I would appreciate it if someone could help me find a resolution.

Additional info:

journalctl -xeu docker.service
Feb 25 19:35:19 ubuntu dockerd[54368]: time="2025-02-25T19:35:19.756023121-05:00" level=info msg="detected 127.0.0.53 nameserver, assuming systemd-resolved, so using resolv.conf: /run/systemd/resolve/resolv.conf"
Feb 25 19:35:19 ubuntu dockerd[54368]: time="2025-02-25T19:35:19.815019179-05:00" level=info msg="[graphdriver] using prior storage driver: overlay2"
Feb 25 19:35:19 ubuntu dockerd[54368]: time="2025-02-25T19:35:19.815364541-05:00" level=info msg="Loading containers: start."
Feb 25 19:35:19 ubuntu dockerd[54368]: time="2025-02-25T19:35:19.818522458-05:00" level=warning msg="Could not load necessary modules for IPSEC rules: protocol not supported"
Feb 25 19:35:19 ubuntu dockerd[54368]: time="2025-02-25T19:35:19.851715359-05:00" level=info msg="stopping event stream following graceful shutdown" error="<nil>" module=libcontainerd namespace=moby
Feb 25 19:35:19 ubuntu dockerd[54368]: failed to start daemon: Error initializing network controller: error obtaining controller instance: failed to register "bridge" driver: invalid argument
Feb 25 19:35:19 ubuntu systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ An ExecStart= process belonging to unit docker.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
Feb 25 19:35:19 ubuntu systemd[1]: docker.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit docker.service has entered the 'failed' state with result 'exit-code'.
Feb 25 19:35:19 ubuntu systemd[1]: Failed to start Docker Application Container Engine.
░░ Subject: A start job for unit docker.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit docker.service has finished with a failure.
░░ 
░░ The job identifier is 131700 and the job result is failed.
Feb 25 19:35:21 ubuntu systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ Automatic restarting of the unit docker.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Feb 25 19:35:21 ubuntu systemd[1]: Stopped Docker Application Container Engine.
░░ Subject: A stop job for unit docker.service has finished
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A stop job for unit docker.service has finished.
░░ 
░░ The job identifier is 131783 and the job result is done.
Feb 25 19:35:21 ubuntu systemd[1]: docker.service: Start request repeated too quickly.
Feb 25 19:35:21 ubuntu systemd[1]: docker.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit docker.service has entered the 'failed' state with result 'exit-code'.
Feb 25 19:35:21 ubuntu systemd[1]: Failed to start Docker Application Container Engine.
░░ Subject: A start job for unit docker.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit docker.service has finished with a failure.
░░ 
░░ The job identifier is 131783 and the job result is failed.
lines 1530-1587/1587 (END)
3

Hi,
If the device cannot be flashed/booted, please refer to the page to get uart log from the device:
Jetson/General debug - eLinux.org
And get logs of host PC and Jetson device for reference. If you are using custom board, you can compare uart log of developer kit and custom board to get more information.
Also please check FAQs:
Jetson AGX Orin FAQ
If possible, we would suggest follow quick start in developer guide to re-flash the system:
Quick Start — NVIDIA Jetson Linux Developer Guide 1 documentation
And see if the issue still persists on a clean-flashed system.
Thanks!

5

Hi,

This is a known issue due to the latest docker release last week.
Our internal team is actively working on the fix.

For now, please check the below comment for the temporal solution:

Thanks.