Greetings,
UPDATE: I was about post the following but I think I found my issue. I'm posting anyway in the event someone else runs into this issue. The clue was the
ORIGINAL PROPOSED POST:
I have a strange problem that out of no where started within minutes of having created several other containers. I know, a bit cliché, we've heard it a thousand times. But really, no change to the PVE host or DHCP service. I had spun up several LXC Containers just prior with the same Ubuntu 24.04 template. This Proxmox host has only one bridge and no vlans, so simple simple. When the container boots, no IP Address is pulled from DHCP. DHCP service is working without question as other devices pull an IP w/o issue, even the previously created containers.
I can recreate issue repeatedly creating a new container:
So, any thoughts on 1) why the previously 4 Ubuntu containers I created pulled an IP Address from DHCP and then container 5 won't, using the same template. Even setting the IP Address manually on creation has no affect. If I've left any config or detail needed to consider this issue, I'll promptly provide on request.
Thank you very much
# Container
# PVE Host
UPDATE: I was about post the following but I think I found my issue. I'm posting anyway in the event someone else runs into this issue. The clue was the
(code=exited, status=226/NAMESPACE) in the systemctl restart systemd-network command. It turns out that the Nesting feature needs to be enabled on the container. I don't recall that being a requirement in any of the previous containers I've created over the years. And in fact, the Debian test container I created does not have the Nesting feature enabled but did pull an IP as expected. And it turns out that the Nesting feature was enabled on the previous 4 Ubuntu containers I created. A detail I overlooked as I worked to trouble shoot the issue. However, I don't recall specifically setting the Nesting option. Perhaps I'm having a mental moment or something. I am interested in knowing why the Nesting feature must be enabled using the Ubuntu 24.04 template and not when using the Debian 12 template. Anyway, peruse the detail below and offer any comments, they would be greatly appreciated.ORIGINAL PROPOSED POST:
I have a strange problem that out of no where started within minutes of having created several other containers. I know, a bit cliché, we've heard it a thousand times. But really, no change to the PVE host or DHCP service. I had spun up several LXC Containers just prior with the same Ubuntu 24.04 template. This Proxmox host has only one bridge and no vlans, so simple simple. When the container boots, no IP Address is pulled from DHCP. DHCP service is working without question as other devices pull an IP w/o issue, even the previously created containers.
I can recreate issue repeatedly creating a new container:
- Create a new container, set it's network settings to all defaults, selecting the IPv4 option to DHCP, domain and dns to what I always do. Boot... no IP pulled from DHCP
- Create a new container and manually set the IP address statically, still no IP address on the interface
- Verify /etc/systemd/network/eth0.network is created by Proxmox. Still no IP address on the interface after rebooting. I can issue an
ip link set eth0 upand no change. However, issuing asystemctl restart systemd-network.serviceresults in an error. - So I decided to try Debian 12. Followed same steps to create a privileged container with IPv4 set to DHCP, domain and dns. When the container comes up, it has pulled an IP Address from DHCP.
So, any thoughts on 1) why the previously 4 Ubuntu containers I created pulled an IP Address from DHCP and then container 5 won't, using the same template. Even setting the IP Address manually on creation has no affect. If I've left any config or detail needed to consider this issue, I'll promptly provide on request.
Thank you very much
# Container
Bash:
root@ubuntu:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: eth0@if16: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether bc:24:11:5e:11:79 brd ff:ff:ff:ff:ff:ff link-netnsid 0
root@ubuntu:~# ip link set eth0 up
root@ubuntu:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: eth0@if16: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether bc:24:11:5e:11:79 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet6 fe80::be24:11ff:fe5e:1179/64 scope link
valid_lft forever preferred_lft forever
Bash:
root@ubuntu:~# systemctl status systemd-networkd.service
× systemd-networkd.service - Network Configuration
Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Tue 2025-06-10 16:36:56 UTC; 5s ago
TriggeredBy: × systemd-networkd.socket
Docs: man:systemd-networkd.service(8)
man:org.freedesktop.network1(5)
Process: 574 ExecStart=/usr/lib/systemd/systemd-networkd (code=exited, status=226/NAMESPACE)
Main PID: 574 (code=exited, status=226/NAMESPACE)
FD Store: 0 (limit: 512)
CPU: 5ms
Jun 10 16:36:56 ubuntu systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 5.
Jun 10 16:36:56 ubuntu systemd[1]: systemd-networkd.service: Start request repeated too quickly.
Jun 10 16:36:56 ubuntu systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
Jun 10 16:36:56 ubuntu systemd[1]: Failed to start systemd-networkd.service - Network Configuration.
root@ubuntu:~# cat /etc/systemd/network/eth0.network
[Match]
Name = eth0
[Network]
Description = Interface eth0 autoconfigured by PVE
Address = 10.13.37.129/24
Gateway = 10.13.37.1
DHCP = no
IPv6AcceptRA = false# PVE Host
Bash:
root@pve6:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback
iface eno1 inet manual
auto vmbr0
iface vmbr0 inet static
address 10.13.37.26/24
gateway 10.13.37.1
bridge-ports eno1
bridge-stp off
bridge-fd 0
source /etc/network/interfaces.d/*
root@pve6:~#
Bash:
root@pve6:~# ls -alF /etc/network/interfaces.d/
total 8
drwxr-xr-x 2 root root 4096 Nov 15 2024 ./
drwxr-xr-x 8 root root 4096 Feb 24 11:02 ../
Bash:
root@pve6:~# cat /etc/pve/lxc/205.conf
arch: amd64
cores: 2
hostname: ubuntu
memory: 1024
nameserver: 1.1.1.1 1.0.0.1
net0: name=eth0,bridge=vmbr0,firewall=1,gw=10.13.37.1,hwaddr=BC:24:11:5E:11:79,ip=10.13.37.129/24,type=veth
ostype: ubuntu
rootfs: pve6-LocalStore:subvol-205-disk-0,size=10G
searchdomain: <redacted>
swap: 512