Docker daemon stops after server update (Ubuntu 22.04.5 LTS)

General
1

After updating server docker stopped.

systemctl --user status docker.service

gives:

 docker.service - Docker Application Container Engine (Rootless)
     Loaded: loaded (/home/ted/.config/systemd/user/docker.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Tue 2025-03-04 12:56:57 +03; 1h 40min ago
       Docs: https://docs.docker.com/go/rootless/
    Process: 1675 ExecStart=/usr/bin/dockerd-rootless.sh (code=exited, status=1/FAILURE)
   Main PID: 1675 (code=exited, status=1/FAILURE)
        CPU: 166ms

Mar 04 12:56:57 nrmbrg1 systemd[995]: docker.service: Scheduled restart job, restart counter is at 3.
Mar 04 12:56:57 nrmbrg1 systemd[995]: Stopped Docker Application Container Engine (Rootless).
Mar 04 12:56:57 nrmbrg1 systemd[995]: docker.service: Start request repeated too quickly.
Mar 04 12:56:57 nrmbrg1 systemd[995]: docker.service: Failed with result 'exit-code'.
Mar 04 12:56:57 nrmbrg1 systemd[995]: Failed to start Docker Application Container Engine (Rootless).

journalctl --user -xeu docker.service

returns:

The job identifier is 302 and the job result is done.
Mar 04 17:39:21 nrmbrg1 systemd[995]: docker.service: Start request repeated too quickly.
Mar 04 17:39:21 nrmbrg1 systemd[995]: docker.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit UNIT has entered the 'failed' state with result 'exit-code'.
Mar 04 17:39:21 nrmbrg1 systemd[995]: Failed to start Docker Application Container Engine (Rootless).
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit UNIT has finished with a failure.
░░
░░ The job identifier is 302 and the job result is failed.

I’m considering to rebuild the server from backup/snapshot. Should I do it?

2

Please, read this post to get the real logs

PS.: Please, use code blocks for logs too. If you quote the logs it won’t be the same in a forum message. I fixed it for you.

3

Hi Thanks…
I saw all those posts with no help.

I figured that the problem was related to the mismatching versions of the update packages as explained here (also the solution is here):
missing “rootlesskit-docker-proxy.sh” after update

In summary, “rootlesskit-docker-proxy.sh” was not in where it is supposed to be (update screwed it).

I was always nervous with docker updates and finally shit hit the fan. So I put docker related updates on hold as you suggested in another post of yours like:

apt-mark hold docker-ce docker-ce-cli docker-ce-rootless-extras

Please verify that this “hold” enough for docker related updates. Should I add other packages in the above command line?

Once again thank you for extending the helping hand…
Rgrds

4

If you accidentally updated a package but not the other, then it is enough as other packages have different versioning strategy. If you are really affraid of any updates, you can hold all the packages mentioned in the official installation guide in the documentation. Since only one package was updated on your machine, holding the package might not help if you ever decide updating one package forgeting the others.

So the three mentioned packages should have the same version. How you achieve that is up to you, but in general, yes, holding those three packages is a good idea. Holding others could be unnecessary

5

Thank you so much … :+1: