Docker stopped working after jetpack update + ssd mount

tzaguyapa · February 10, 2022, 5:22pm

Hi,
I upgraded the jetpack version from 4.4 to 4.6 (OTA); and mounted an ssd to boot from.
followed the articles upgrade to minor release and run from ssd respectively.
Now I get the error Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
systemctl status docker gives
`docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2022-02-11 03:52:01 AEDT; 26min ago
Docs: https://docs.docker.com
Process: 18616 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
Main PID: 18616 (code=exited, status=1/FAILURE)

Feb 11 03:51:59 desktop systemd[1]: Failed to start Docker Application Container Engine.
Feb 11 03:52:01 desktop systemd[1]: docker.service: Service hold-off time over, scheduling restart.
Feb 11 03:52:01 desktop systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Feb 11 03:52:01 desktop systemd[1]: Stopped Docker Application Container Engine.
Feb 11 03:52:01 desktop systemd[1]: docker.service: Start request repeated too quickly.
Feb 11 03:52:01 desktop systemd[1]: docker.service: Failed with result ‘exit-code’.
Feb 11 03:52:01 desktop systemd[1]: Failed to start Docker Application Container Engine.
`

Any help would be great.

AastaLLL · February 11, 2022, 3:29am

Hi,

Could you try to restart it and check the status?

$ sudo systemctl restart docker

Thanks.

tzaguyapa · February 13, 2022, 11:44am

Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.

for systemctl status docker.service it gives

docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2022-02-13 22:41:07 AEDT; 21s ago
     Docs: https://docs.docker.com
  Process: 16431 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
 Main PID: 16431 (code=exited, status=1/FAILURE)

Feb 13 22:41:07 ddi-nx systemd[1]: docker.service: Service hold-off time over, scheduling restart.
Feb 13 22:41:07 ddi-nx systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Feb 13 22:41:07 ddi-nx systemd[1]: Stopped Docker Application Container Engine.
Feb 13 22:41:07 ddi-nx systemd[1]: docker.service: Start request repeated too quickly.
Feb 13 22:41:07 ddi-nx systemd[1]: docker.service: Failed with result 'exit-code'.
Feb 13 22:41:07 ddi-nx systemd[1]: Failed to start Docker Application Container Engine.

for journalctl -xe it gives

-- Subject: Unit docker.service has begun start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit docker.service has begun starting up.
Feb 13 22:41:05 ddi-nx dockerd[16431]: time="2022-02-13T22:41:05.589476763+11:00" level=info msg="Starting up"
Feb 13 22:41:05 ddi-nx dockerd[16431]: time="2022-02-13T22:41:05.593264226+11:00" level=info msg="parsed scheme: \"unix\"" module=grpc
Feb 13 22:41:05 ddi-nx dockerd[16431]: time="2022-02-13T22:41:05.593492101+11:00" level=info msg="scheme \"unix\" not registered, fallback to default scheme" module=grpc
Feb 13 22:41:05 ddi-nx dockerd[16431]: time="2022-02-13T22:41:05.593644454+11:00" level=info msg="ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock  <nil> 0 <nil>}] <nil> <nil>}"
Feb 13 22:41:05 ddi-nx dockerd[16431]: time="2022-02-13T22:41:05.593708327+11:00" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc
Feb 13 22:41:05 ddi-nx dockerd[16431]: time="2022-02-13T22:41:05.599096127+11:00" level=info msg="parsed scheme: \"unix\"" module=grpc
Feb 13 22:41:05 ddi-nx dockerd[16431]: time="2022-02-13T22:41:05.599172223+11:00" level=info msg="scheme \"unix\" not registered, fallback to default scheme" module=grpc
Feb 13 22:41:05 ddi-nx dockerd[16431]: time="2022-02-13T22:41:05.599236864+11:00" level=info msg="ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock  <nil> 0 <nil>}] <nil> <nil>}"
Feb 13 22:41:05 ddi-nx dockerd[16431]: time="2022-02-13T22:41:05.599310465+11:00" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc
Feb 13 22:41:05 ddi-nx dockerd[16431]: failed to start daemon: error initializing graphdriver: /var/lib/docker contains several valid graphdrivers: overlay2, devicemapper; Please cleanup or explicitly choose sto
Feb 13 22:41:05 ddi-nx dockerd[16431]: time="2022-02-13T22:41:05.629235254+11:00" level=info msg="stopping event stream following graceful shutdown" error="context canceled" module=libcontainerd namespace=plugin
Feb 13 22:41:05 ddi-nx systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Feb 13 22:41:05 ddi-nx systemd[1]: docker.service: Failed with result 'exit-code'.
Feb 13 22:41:05 ddi-nx 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.
-- 
-- The result is RESULT.
Feb 13 22:41:07 ddi-nx systemd[1]: docker.service: Service hold-off time over, scheduling restart.
Feb 13 22:41:07 ddi-nx 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 13 22:41:07 ddi-nx systemd[1]: Stopped Docker Application Container Engine.
-- Subject: Unit docker.service has finished shutting down
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit docker.service has finished shutting down.
Feb 13 22:41:07 ddi-nx systemd[1]: docker.service: Start request repeated too quickly.
Feb 13 22:41:07 ddi-nx systemd[1]: docker.service: Failed with result 'exit-code'.
Feb 13 22:41:07 ddi-nx 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.
-- 
-- The result is RESULT.
Feb 13 22:41:07 ddi-nx systemd[1]: docker.socket: Failed with result 'service-start-limit-hit'.
Feb 13 22:41:29 ddi-nx sudo[16491]:      ddi : TTY=pts/0 ; PWD=/home/ddi ; USER=root ; COMMAND=/bin/systemctl status docker.service
Feb 13 22:41:29 ddi-nx sudo[16491]: pam_unix(sudo:session): session opened for user root by ddi(uid=0)
Feb 13 22:41:29 ddi-nx sudo[16491]: pam_unix(sudo:session): session closed for user root

tzaguyapa · February 14, 2022, 5:09am

Fixed it by specifying the storage driver to be used by the daemon.

dockerd -s overlay2

system · March 9, 2022, 1:45am

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