Docker not starting on L4T 32.7.1 (Jetpack 4.6.1)

[bmsp]

We have encountered an issue when attempting start Docker on the Jetpack 4.6.1 (L4T 32.7.1) release.

We installed it like so, which follows the guidance in this other post which also encountered an issue with Docker on this Jetpack version on the TX2.

sudo apt install nvidia-container*

However it appears to be failing to start. See the journalctl -xe -u docker output:

Apr 12 23:01:47 localhost dockerd[13027]: time="2022-04-12T23:01:47.883046144Z" level=info msg="Starting up"
Apr 12 23:01:47 localhost dockerd[13027]: time="2022-04-12T23:01:47.895961640Z" level=info msg="parsed scheme: \"unix\"" module=grpc
Apr 12 23:01:47 localhost dockerd[13027]: time="2022-04-12T23:01:47.896074121Z" level=info msg="scheme \"unix\" not registered, fallback to default sch
Apr 12 23:01:47 localhost dockerd[13027]: time="2022-04-12T23:01:47.896180905Z" level=info msg="ccResolverWrapper: sending update to cc: {[{unix:///run
Apr 12 23:01:47 localhost dockerd[13027]: time="2022-04-12T23:01:47.896240842Z" level=info msg="ClientConn switching balancer to \"pick_first\"" module
Apr 12 23:01:47 localhost dockerd[13027]: time="2022-04-12T23:01:47.927188535Z" level=info msg="parsed scheme: \"unix\"" module=grpc
Apr 12 23:01:47 localhost dockerd[13027]: time="2022-04-12T23:01:47.929065409Z" level=info msg="scheme \"unix\" not registered, fallback to default sch
Apr 12 23:01:47 localhost dockerd[13027]: time="2022-04-12T23:01:47.933342713Z" level=info msg="ccResolverWrapper: sending update to cc: {[{unix:///run
Apr 12 23:01:47 localhost dockerd[13027]: time="2022-04-12T23:01:47.933727932Z" level=info msg="ClientConn switching balancer to \"pick_first\"" module
Apr 12 23:01:48 localhost dockerd[13027]: time="2022-04-12T23:01:48.098275094Z" level=error msg="[graphdriver] prior storage driver devicemapper failed
Apr 12 23:01:48 localhost dockerd[13027]: failed to start daemon: error initializing graphdriver: devicemapper: Error running deviceCreate (CreatePool)
Apr 12 23:01:48 localhost systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Apr 12 23:01:48 localhost systemd[1]: docker.service: Failed with result 'exit-code'.
Apr 12 23:01:48 localhost systemd[1]: Failed to start Docker Application Container Engine.
-- Subject: Unit docker.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit docker.service has failed.

Additionally dmesg appears to complain about the following when we attempt to restart Docker:

[10199.843808] device-mapper: table: 253:0: thin-pool: unknown target type
[10199.843993] device-mapper: ioctl: error adding target to table
[10202.166229] device-mapper: table: 253:0: thin-pool: unknown target type
[10202.166395] device-mapper: ioctl: error adding target to table
[10204.927323] device-mapper: table: 253:0: thin-pool: unknown target type
[10204.927483] device-mapper: ioctl: error adding target to table

We can attempt to restart Docker using systemctl:

sudo systemctl restart docker

We were unable to successfully start Docker. Has anyone encountered this issue and way to resolve it?

Thank you!

[AastaLLL]

Hi,

Would you mind sharing the output for the below commands with us first?

$ sudo apt show nvidia-jetpack
$ sudo docker -d

We test the journalctl -xe -u docker command internally.
It can work without the devicemapper error in our environment.

Thanks.

[bmsp]

Hello,

We’re not fully sure why, but apparently installing the nvidia-jetpack package resolved the issue. We had flashed a more minimal version of L4T.

Thank you!