Hi, I see two suspects worth analyzing:
- docker.service @1min 38.061s +40.679s
- systemd-journal-flush.service @7.687s +1min 10.375s
While I know nothing about the first, the latter is likely due to large or highly fragmented journal files and/or slow disk.
I had similar problems with BTRFS on small/slow laptop disks.
To see if that is your case, please see the result of:
journalctl -b |grep "Time spent on flushing"
and possibly the lines of the journal near that time in the boot process.
Then look at the files in the /var/log/journal/<a long number unique to your system> if they are larger than, say 100 MB each or if they show something else unusual.
If that is your case too, you can edit the journal settings in a way to limit the offence…