On Sat, 11 Feb 2023 14:21:27 +0100 Beat Bolli <i...@drbeat.li> wrote: > My host does not have wpa_supplicant installed (LAN only) and now dhcpcd > cannot be started by systemd: > > Feb 11 11:51:55 zbox systemd[1]: Starting dhcpcd.service - DHCP Client > Daemon on all interfaces... > Feb 11 11:51:55 zbox systemd[547]: dhcpcd.service: Failed to set up > mount namespacing: /run/systemd/unit-root/etc/wpa_supplicant: No such > file or directory > Feb 11 11:51:55 zbox systemd[547]: dhcpcd.service: Failed at step > NAMESPACE spawning /usr/sbin/dhcpcd: No such file or directory > Feb 11 11:51:55 zbox systemd[1]: dhcpcd.service: Control process exited, > code=exited, status=226/NAMESPACE > Feb 11 11:51:55 zbox systemd[1]: dhcpcd.service: Failed with result > 'exit-code'. > Feb 11 11:51:55 zbox systemd[1]: Failed to start dhcpcd.service - DHCP > Client Daemon on all interfaces. > > It seems that the directory /etc/wpa_supplicant has to exist if it's > listed in ReadWritePaths.
Good to know. We will now Depends on wpasupplicant. > Workaround: sudo mkdir /etc/wpa_supplicant That would probably work too, but given how dhcpcd is designed to interact with wpsupplicant anyhow (it can load SSID profiles, for instance), I'd rather make it Depends on it. Martin-Éric
