I have configured several containers with static ips using systemd-networkd. Config looks like this:
luigi@HomeServer:~$ incus profile show ext_network
config: {}
description: “”
devices:
eth0:
name: eth0
nictype: bridged
parent: mainbr0
type: nic
name: ext_network
used_by:
- /1.0/instances/Docker
- /1.0/instances/Debian12Cloud
- /1.0/instances/Python
- /1.0/instances/MyDesktop
root@Python:~# cat /etc/systemd/network/10-cloud-init-eth0.network
[Match]
Name=eth0
[Network]
Address=10.10.0.52/24
Gateway=10.10.0.1
DNS=10.10.0.1
Everytime I restart my incus host none of these containers receive an iP, If I restart the container or I restart systemd-networkd they do receive it. I have checked all revelant logs for systemd-networkd that I know of and I still cannot determine whats going on. I started doing some troubleshooting inside the container logs as follows:
root@Python:~# dmesg
dmesg: read kernel buffer failed: Operation not permitted
journalctl shows a bunch of errors like the following:
Apr 17 00:42:14 Python udevadm[136]: event_source: Failed to write ‘add’ to ‘/sys/bus/event_source/uevent’: Permission denied
Apr 17 00:42:14 Python udevadm[136]: gpio: Failed to write ‘add’ to ‘/sys/bus/gpio/uevent’: Permission denied
Apr 17 00:42:14 Python udevadm[136]: hardware_error_device: Failed to write ‘add’ to ‘/sys/bus/acpi/drivers/hardware_error_device/uevent’: Permission denied
Apr 17 00:50:44 MyDesktop udevadm[137]: LNXSYSTM:00: Failed to write ‘add’ to ‘/sys/devices/LNXSYSTM:00/uevent’: Permission denied
Apr 17 00:50:44 MyDesktop udevadm[137]: LNXPWRBN:00: Failed to write ‘add’ to ‘/sys/devices/LNXSYSTM:00/LNXPWRBN:00/uevent’: Permission denied
Apr 17 00:58:28 MyDesktop udevadm[133]: RTL8201F Fast Ethernet: Failed to write ‘add’ to ‘/sys/bus/mdio_bus/drivers/RTL8201F Fast Ethernet/uevent’: Permissio>
Apr 17 00:58:28 MyDesktop udevadm[133]: RTL8208 Fast Ethernet: Failed to write ‘add’ to ‘/sys/bus/mdio_bus/drivers/RTL8208 Fast Ethernet/uevent’: Permission >
Apr 17 00:58:28 MyDesktop udevadm[133]: RTL8211 Gigabit Ethernet: Failed to write ‘add’ to ‘/sys/bus/mdio_bus/drivers/RTL8211 Gigabit Ethernet/uevent’: Permi>
Apr 17 00:58:28 MyDesktop udevadm[133]: RTL8211B Gigabit Ethernet: Failed to write ‘add’ to ‘/sys/bus/mdio_bus/drivers/RTL8211B Gigabit Ethernet/uevent’: Per>
Apr 17 00:58:28 MyDesktop udevadm[133]: RTL8211C Gigabit Ethernet: Failed to write ‘add’ to ‘/sys/bus/mdio_bus/drivers/RTL8211C Gigabit Ethernet/uevent’: Per>
Apr 17 00:58:28 MyDesktop udevadm[133]: RTL8211DN Gigabit Ethernet: Failed to write ‘add’ to ‘/sys/bus/mdio_bus/drivers/RTL8211DN Gigabit Ethernet/uevent’: P>
Apr 17 00:58:28 MyDesktop udevadm[133]: RTL8211E Gigabit Ethernet: Failed to write ‘add’ to ‘/sys/bus/mdio_bus/drivers/RTL8211E Gigabit Ethernet/uevent’: Per>
Apr 17 00:58:28 MyDesktop udevadm[133]: RTL8211F Gigabit Ethernet: Failed to write ‘add’ to ‘/sys/bus/mdio_bus/drivers/RTL8211F Gigabit Ethernet/uevent’: Per>
Apr 17 00:58:28 MyDesktop udevadm[133]: RTL8211F-VD Gigabit Ethernet: Failed to write ‘add’ to '/sys/bus/mdio_bus/drivers/RTL8211F-VD Gigabit Ethernet/uevent>
Apr 17 00:58:28 MyDesktop udevadm[133]: RTL8221B-VB-CG 2.5Gbps PHY: Failed to write ‘add’ to ‘/sys/bus/mdio_bus/drivers/RTL8221B-VB-CG 2.5Gbps PHY/uevent’: P>
Apr 17 00:58:28 MyDesktop udevadm[133]: RTL8221B-VM-CG 2.5Gbps PHY: Failed to write ‘add’ to ‘/sys/bus/mdio_bus/drivers/RTL8221B-VM-CG 2.5Gbps PHY/uevent’: P>
Apr 17 00:58:28 MyDesktop udevadm[133]: RTL8226 2.5Gbps PHY: Failed to write ‘add’ to ‘/sys/bus/mdio_bus/drivers/RTL8226 2.5Gbps PHY/uevent’: Permission deni>
Apr 17 00:58:28 MyDesktop udevadm[133]: RTL8226-CG 2.5Gbps PHY: Failed to write ‘add’ to ‘/sys/bus/mdio_bus/drivers/RTL8226-CG 2.5Gbps PHY/uevent’: Permissio>
Apr 17 00:58:28 MyDesktop udevadm[133]: RTL8226B-CG_RTL8221B-CG 2.5Gbps PHY: Failed to write ‘add’ to '/sys/bus/mdio_bus/drivers/RTL
~# systemctl status systemd-networkd
○ systemd-networkd.service - Network Configuration
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; preset: enabled)
Drop-In: /run/systemd/system/service.d
└─zzz-lxc-service.conf
Active: inactive (dead)
TriggeredBy: ● systemd-networkd.socket
Docs: man:systemd-networkd.service(8)
man:org.freedesktop.network1(5)
if I do a incus restart all I see all seems to work and all containers get either their respective static ip or dynamic ip. This is only happening when I restart the host.
±--------------±--------±---------------------±-----±----------±----------+
| NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS |
±--------------±--------±---------------------±-----±----------±----------+
| Debian12Cloud | STOPPED | | | CONTAINER | 1 |
±--------------±--------±---------------------±-----±----------±----------+
| Docker | RUNNING | 172.17.0.1 (docker0) | | CONTAINER | 0 |
| | | 10.10.0.51 (eth0) | | | |
±--------------±--------±---------------------±-----±----------±----------+
| MyDesktop | RUNNING | 10.10.0.106 (eth0) | | CONTAINER | 0 |
±--------------±--------±---------------------±-----±----------±----------+
| Python | RUNNING | 10.10.0.52 (eth0) | | CONTAINER | 0 |
±--------------±--------±---------------------±-----±----------±----------+
any other ideas? If I restart networkd or I reboot the client it works, but not upon initial host boot. I do notice one thing, one of my other containers has docker installed, which does seem to work upon boot. I read on the docs that docker can cause problems while running on the host. On the host I only run incus. Does it matter if the host is running ENI etc/network/interfaces and the containers run systems?