Having issues with docker not working due to too many restarts

General system Newbie
1

I am unable to use the docker daemon I have running with systemd.

This is what I see when I run journalctl -xeu docker.service:

Jul 19 23:50:24 Framework 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: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ Automatic restarting of the unit docker.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Jul 19 23:50:24 Framework systemd[1]: docker.service: Start request repeated too quickly.
Jul 19 23:50:24 Framework systemd[1]: docker.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit docker.service has entered the 'failed' state with result 'exit-code'.
Jul 19 23:50:24 Framework systemd[1]: Failed to start Docker Application Container Engine.
░░ Subject: A start job for unit docker.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit docker.service has finished with a failure.
░░ 
░░ The job identifier is 1735 and the job result is failed.

This is what I see when I run journalctl -xeu docker.socket:

Jul 19 23:49:47 Framework systemd[1]: Starting Docker Socket for the API...
░░ Subject: A start job for unit docker.socket has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit docker.socket has begun execution.
░░ 
░░ The job identifier is 268.
Jul 19 23:49:47 Framework systemd[1]: Listening on Docker Socket for the API.
░░ Subject: A start job for unit docker.socket has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit docker.socket has finished successfully.
░░ 
░░ The job identifier is 268.
Jul 19 23:50:24 Framework systemd[1]: docker.socket: Failed with result 'service-start-limit-hit'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit docker.socket has entered the 'failed' state with result 'service-start-limit-hit'.

I thought I had messed something up on my existing install, so I reinstalled Endeavour using the latest install ISO from endeavouros.com and am still running into this problem after installing docker.

Here is some information about my system:

                     ./o.                   insomnia@Framework
                   ./sssso-                 ------------------
                 `:osssssss+-               OS: EndeavourOS x86_64
               `:+sssssssssso/.             Host: Laptop 16 (AMD Ryzen 7040 Series) (A7)
             `-/ossssssssssssso/.           Kernel: Linux 6.9.10-arch1-1
           `-/+sssssssssssssssso+:`         Uptime: 10 hours, 37 mins
         `-:/+sssssssssssssssssso+/.        Packages: 1098 (pacman)
       `.://osssssssssssssssssssso++-       Shell: fish 3.7.1
      .://+ssssssssssssssssssssssso++:      Display (BOE0BC9): 2560x1600 @ 165Hz (as 1706x1066) [Buil]
    .:///ossssssssssssssssssssssssso++:     DE: KDE Plasma 6.1.3
  `:////ssssssssssssssssssssssssssso+++.    WM: KWin (Wayland)
`-////+ssssssssssssssssssssssssssso++++-    WM Theme: Breeze
 `..-+oosssssssssssssssssssssssso+++++/`    Theme: Breeze (Dark) [Qt], Breeze-Dark [GTK2], Breeze [GT]
   ./++++++++++++++++++++++++++++++/:.      Icons: breeze-dark [Qt], breeze-dark [GTK2/3/4]
  `:::::::::::::::::::::::::------``        Font: Noto Sans (10pt) [Qt], Noto Sans (10pt) [GTK2/3/4]
                                            Cursor: breeze (24px)
                                            Terminal: konsole 24.5.2
                                            CPU: AMD Ryzen 7 7840HS w/ Radeon 780M Graphics (16) @ 5.z
                                            GPU: AMD Radeon 780M [Integrated]
                                            Memory: 4.89 GiB / 14.82 GiB (33%)
                                            Swap: 0 B / 16.30 GiB (0%)
                                            Disk (/): 43.55 GiB / 898.79 GiB (5%) - ext4
                                            Local IP (wlan0): 192.168.1.251/24
                                            Battery: 100% [AC Connected]
                                            Locale: en_US.UTF-8

I can provide more information if necessary.

2

Hey, you posted just the last lines of the journal, but I’m guessing you’re having the same problem I had until just a couple of minutes ago. Just to be sure, run journalctl -xeu docker | grep 'same bridge name', if it outputs several lines and its time and date corresponds to when you tried to start docker, then yes, it might be the same problem.

It seems an update broke things. This happened in all my computers.

What I did to fix it was to remove (I actually backed up somewhere else just in case) the contents of /var/lib/docker/network and started docker again.

I googled a bit, and it seems you may have to rebuild some of your containers if they are expecting to connect to the former docker0 bridge for them to work. Although if you reinstalled your whole system, this might not be an issue for you.

And just a little advise if it doesn’t bother you (since you chose the Newbie category). Don’t freakout when things stop working in any arch based distro after an update, when this happens, usually a new update will address the issue an fix it, and if it doesn’t, eventually you’ll find people is posting about it somewhere. Docker died on me yesterday and since I didn’t make any changes to it, I assumed it was an update issue and waited until today, no update fixed it, then I started the troubleshooting.

References:
Stack Overflow
Stack Exchange

Oh, and sorry for my english. I’m short of time to make this better, but I didn’t wanted to left it unanswered knowing this could help.

Good luck!

4 Likes
4

Thank you! I was banging my head trying to figure this one out!

1 Like