Docker slow to start after reboot

Nefertiti · Jul 7th 2023

I had this issue before got it fix by itself but again after reboot docker service start up take 3 to 4 min to start up, after this everything is normal?

Nefertiti · Jul 7th 2023

Code

according to this https://www.tecmint.com/systemd-analyze-monitor-linux-bootup-performance/

Code

~# systemd-analyze
Startup finished in 7.151s (firmware) + 4.448s (loader) + 2.637s (kernel) + 2min 2.595s (userspace)                                             = 2min 16.832s
graphical.target reached after 2min 2.058s in userspace.
root@openmediavault:~# systemd-analyze
Startup finished in 7.151s (firmware) + 4.448s (loader) + 2.637s (kernel) + 2min 2.595s (userspace)                                             = 2min 16.832s
graphical.target reached after 2min 2.058s in userspace.

Code

systemd-analyze blame
1min 54.433s docker.service
 1min 2.198s openmediavault-issue.service
      5.793s folder2ram_startup.service
      2.832s systemd-networkd-wait-online.service
      2.209s postgresql@12-main.service
       710ms systemd-fsck@dev-disk-by\x2duuid-9cd27ed0\x2def9a\x2d4346\x2dae1e\x2d5e835ba05832.service
       527ms quotaon.service
       464ms openmediavault-beep-up.service
       214ms dev-nvme0n1p2.device
       207ms systemd-networkd.service
       187ms srv-dev\x2ddisk\x2dby\x2duuid\x2da608fdc2\x2d69d6\x2d4c61\x2db1e0\x2d8822162bb8b8.mount
       187ms containerd.service
       185ms srv-dev\x2ddisk\x2dby\x2duuid\x2da8d62abf\x2d6358\x2d488e\x2d9239\x2d7e1e82738c84.mount
       183ms srv-dev\x2ddisk\x2dby\x2duuid\x2d9cd27ed0\x2def9a\x2d4346\x2dae1e\x2d5e835ba05832.mount
       183ms srv-dev\x2ddisk\x2dby\x2duuid\x2dd1e04f7e\x2d9bef\x2d43ae\x2db54f\x2de67137357548.mount
       183ms smbd.service
       182ms srv-dev\x2ddisk\x2dby\x2duuid\x2deaff6590\x2d9d2f\x2d4e14\x2daa25\x2dbd1ee663c7b6.mount
       181ms systemd-fsck@dev-disk-by\x2duuid-a8d62abf\x2d6358\x2d488e\x2d9239\x2d7e1e82738c84.service
       172ms systemd-fsck@dev-disk-by\x2duuid-37d059e6\x2d8189\x2d404a\x2d967b\x2d53afec96bf4f.service
       165ms systemd-fsck@dev-disk-by\x2duuid-eaff6590\x2d9d2f\x2d4e14\x2daa25\x2dbd1ee663c7b6.service
       157ms systemd-sysctl.service
       152ms systemd-fsck@dev-disk-by\x2duuid-a608fdc2\x2d69d6\x2d4c61\x2db1e0\x2d8822162bb8b8.service
       147ms systemd-fsck@dev-disk-by\x2duuid-d1e04f7e\x2d9bef\x2d43ae\x2db54f\x2de67137357548.service
       122ms loadcpufreq.service
       104ms lvm2-monitor.service
        79ms phpsessionclean.service
        74ms systemd-journal-flush.service
        60ms php7.4-fpm.service
        53ms srv-dev\x2ddisk\x2dby\x2duuid\x2d37d059e6\x2d8189\x2d404a\x2d967b\x2d53afec96bf4f.mount
        53ms systemd-udev-trigger.service
        48ms openmediavault-engined.service
        39ms run-rpc_pipefs.mount
        38ms nginx.service
        35ms systemd-resolved.service
        33ms chrony.service
        32ms keyboard-setup.service
        29ms boot-efi.mount
        27ms systemd-udevd.service
        26ms systemd-logind.service
        26ms avahi-daemon.service
        25ms systemd-journald.service
        25ms modprobe@drm.service
        23ms apparmor.service
        23ms monit.service
        23ms srv-dev\x2ddisk\x2dby\x2duuid\x2d1942e416\x2dbbf4\x2d4f33\x2db6a3\x2d00171f82bf75.mount
        20ms e2scrub_reap.service
        20ms srv-dev\x2ddisk\x2dby\x2duuid\x2d2673986a\x2dae3f\x2d49c9\x2dbf92\x2d3fe6011743d8.mount
        19ms dev-hugepages.mount
        19ms networking.service
        17ms dev-mqueue.mount
        16ms var-lib-docker.mount
        15ms systemd-fsck@dev-disk-by\x2duuid-1942e416\x2dbbf4\x2d4f33\x2db6a3\x2d00171f82bf75.service
        15ms srv-dev\x2ddisk\x2dby\x2duuid\x2d37eafd34\x2d8390\x2d4bb5\x2d9d08\x2dc1acfa5fb0ca.mount
        15ms systemd-modules-load.service
        14ms ssh.service
        14ms rrdcached.service
        13ms lm-sensors.service
        13ms dev-disk-by\x2duuid-bbed79c3\x2d7997\x2d4614\x2da40c\x2dc7f3e0f4d47e.swap
        13ms systemd-fsck@dev-disk-by\x2duuid-37eafd34\x2d8390\x2d4bb5\x2d9d08\x2dc1acfa5fb0ca.service
        13ms sys-kernel-debug.mount
        13ms systemd-fsck@dev-disk-by\x2duuid-2673986a\x2dae3f\x2d49c9\x2dbf92\x2d3fe6011743d8.service
        12ms systemd-tmpfiles-setup-dev.service
        12ms collectd.service
        12ms modprobe@efi_pstore.service
        11ms sys-kernel-tracing.mount
        11ms wpa_supplicant.service
         9ms rsyslog.service
         8ms systemd-tmpfiles-clean.service
         8ms kmod-static-nodes.service
         7ms modprobe@fuse.service
         7ms cpufrequtils.service
         7ms systemd-tmpfiles-setup.service
         6ms console-setup.service
         6ms modprobe@configfs.service
         6ms systemd-sysusers.service
         5ms systemd-remount-fs.service
         5ms rpcbind.service
         4ms systemd-random-seed.service
         4ms nfs-config.service
         4ms systemd-update-utmp.service
         3ms openmediavault-cleanup-php.service
         3ms systemd-update-utmp-runlevel.service
         3ms openmediavault-cleanup-monit.service
         3ms tmp.mount
         3ms systemd-quotacheck.service
         2ms postgresql.service
         2ms systemd-user-sessions.service
         1ms ifupdown-pre.service
         1ms nfs-blkmap.service
         1ms sys-kernel-config.mount
         1ms sys-fs-fuse-connections.mount
       614us docker.socket
        63us folder2ram_shutdown.service
        28us blk-availability.service

Display More

Soma · Jul 7th 2023

Suche - openmediavault

Nefertiti · Jul 9th 2023

Thank you but so far cannot get a resolution from it! 😥

Soma · Jul 9th 2023

Quote from Nefertiti

Thank you but so far cannot get a resolution from it! 😥

Output of:

systemd-analyze critical-chain

Stop all containers and triage, one by one and reboot, to see which one is causing the slow start-up.

As for the link I posted, is to disable the openmediavault-issue.service. What it does (IIRC) was taking care of the initial login message on CLI (not needed)

Post

RE: Troubleshooting: openmediavault-issue.service takes too long to start up (slow boot)

[…]

Yes, you can disable it. The openmediavault-issue unit file is only responsible for generating the welcome message.

votdev

Sep 15th 2021

Nefertiti · Jul 11th 2023

Code

 systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @2min 2.077s
└─multi-user.target @2min 2.077s
  └─docker.service @9.003s +1min 53.072s
    └─srv-dev\x2ddisk\x2dby\x2duuid\x2d37d059e6\x2d8189\x2d404a\x2d967b\x2d53afec96bf4f-docker-over>
      └─local-fs-pre.target @497ms
        └─lvm2-monitor.service @356ms +140ms
          └─systemd-journald.socket @336ms
            └─-.mount @239ms
              └─-.slice @239ms

Display More

Soma · Jul 11th 2023

Have you tried what I said on post #5

Quote from Soma

Stop all containers and triage, one by one and reboot, to see which one is causing the slow start-up

The first step would be with ALL containers stopped and reboot.

This will show only how much time the docker.service takes to start.

Take notice of the time delay. (the value from critical-chain info after the +. The above shows docker.service @9.003s +1min 53.072s)

Other thing you can do is on Services-> Compose-> Settings-> click Reinstall Docker.

Maybe some drive is not added to the WaitAllMounts.conf and it takes longer to find it.

Just guessing here and have no more ideas for you other than, deal with it.

Do you reboot that often that you can't live with a 2minute delay without the server?

[EDIT]

After a clean start (proper shutdown/start instead of reboot) what is the output of sudo systemctl status docker.service when everything is already running?

[/EDIT]

Docker slow to start after reboot

Participate now!

Similar Threads

advice on switching from 4 to 6 (new install)

SSH service fails to start on port 22 after some irregular behavior

mdadm: No Arrays found/ lsblk no mounting point?