FS#72741 - [caddy] Remove dependency on systemd-networkd from the service
Attached to Project:
Community Packages
Opened by Vitaliy Kudasov (kuviman) - Sunday, 14 November 2021, 04:09 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:03 GMT
Opened by Vitaliy Kudasov (kuviman) - Sunday, 14 November 2021, 04:09 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:03 GMT
|
Details
Description:
caddy's systemd service Wants=systemd-networkd-wait-online.service which causes systemd-networkd to start In case system is using a different network manager (e.g. NetworkManager) this causes a conflict. The problem is not immediately obvious but networking stops working in docker containers for example |
This task depends upon
Closed by Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:03 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/caddy/issues/1
Saturday, 25 November 2023, 20:03 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/caddy/issues/1
Comment by
Jonas Witschel (diabonas) -
Wednesday, 17 November 2021, 10:16 GMT
systemd-networkd-wait-online.service should indeed not be pulled
in by the service, instead it should depend on
network-online.target (which it already does) as the correct wait
service is enabled automatically when systemd-networkd is
enabled:
https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/#cutthecraphowdoimakesurethatmyservicestartsafterthenetworkisreallyonline