Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
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 Jonas Witschel (diabonas) - Wednesday, 17 November 2021, 10:16 GMT
Opened by Vitaliy Kudasov (kuviman) - Sunday, 14 November 2021, 04:09 GMT
Last edited by Jonas Witschel (diabonas) - Wednesday, 17 November 2021, 10:16 GMT
|
DetailsDescription:
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

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