fix slow startup
DrPsychick opened this issue · 2 comments
DrPsychick commented
it seems systemd is required and causes a timeout
method call time=1585598834.846481 sender=:1.1 -> destination=org.freedesktop.systemd1 serial=2 path=/org/freedesktop/systemd1; interface=org.freedesktop.systemd1.Manager; member=GetDynamicUsers
method call time=1585598834.851244 sender=:1.2 -> destination=org.freedesktop.systemd1 serial=2 path=/org/freedesktop/systemd1; interface=org.freedesktop.systemd1.Manager; member=GetDynamicUsers
method call time=1585598854.951282 sender=:1.4 -> destination=org.freedesktop.systemd1 serial=2 path=/org/freedesktop/systemd1; interface=org.freedesktop.systemd1.Manager; member=GetDynamicUsers
[...]
error time=1585598859.818583 sender=org.freedesktop.DBus -> destination=:1.1 error_name=org.freedesktop.DBus.Error.TimedOut reply_serial=2
string "Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)"
error time=1585598859.818658 sender=org.freedesktop.DBus -> destination=:1.2 error_name=org.freedesktop.DBus.Error.TimedOut reply_serial=2
string "Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)"
error time=1585598859.818695 sender=org.freedesktop.DBus -> destination=:1.4 error_name=org.freedesktop.DBus.Error.TimedOut reply_serial=2
string "Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)"
DrPsychick commented
running systemd in docker seems a bad idea... https://developers.redhat.com/blog/2014/05/05/running-systemd-within-docker-container/
but in this case we do want to run multiple services (cups+avahi+background stuff) all in one container
- either live with the 2 minute startup time
- or fix the systemd dependency
DrPsychick commented
Solution:
- remove dhcp hooks (that trigger timesyncd which requires systemd)
- disable dbus in avahi
fixed with c1fed56