I spent over 8 hours trying to figure out what in the world is going on here. I tried:
1. Creating a container using my previous script so that it should have been exactly like my other containers
2. Creating a container manually using the GUI
3. Configuring networking with DHCP
4. Configuring networking with Static IPs
5. Using the Ubuntu 23.10 template (this works)
6. Using a different distro (Debian) (this also works)
Currently if I attempt to create a container using the Ubuntu 24.10 template, VIA THE UI AND USING THE EXACT SAME SETTINGS (and MAC address) as either a Debian 12.7 or Ubuntu 23.10 template, the 12.7 container works fine and the 23.10 container works fine. However the 24.10 template's bridged ethernet adapter DOES NOT CONNECT.
On the host, with Ubuntu 24.10, the interface is listed as:
51: veth100i0@if2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue master vmbr0 state LOWERLAYERDOWN group default qlen 1000
link/ether <autoassigned_mac_address> brd ff:ff:ff:ff:ff:ff link-netnsid 4
On the container, the interface is listed as:
2: eth0@if51: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether <my_hardcoded_mac_address> brd ff:ff:ff:ff:ff:ff link-netnsid 0
Occasionally I've also noticed that when I create the container from my script, `master vmbr0` no longer shows up on the host and I have to manually set it. This is probably unrelated though but does signify a difference between previous behavior.
Now, here's the extra crazy bit:
If I create an Ubuntu 23.10 container and `do-release-upgrade`, it still works!
So to me, this seems to point to the fact that there is an issue with the 24.10 template's default configuration itself rather than Ubuntu 24.10/Debian 13.
1. Creating a container using my previous script so that it should have been exactly like my other containers
2. Creating a container manually using the GUI
3. Configuring networking with DHCP
4. Configuring networking with Static IPs
5. Using the Ubuntu 23.10 template (this works)
6. Using a different distro (Debian) (this also works)
Currently if I attempt to create a container using the Ubuntu 24.10 template, VIA THE UI AND USING THE EXACT SAME SETTINGS (and MAC address) as either a Debian 12.7 or Ubuntu 23.10 template, the 12.7 container works fine and the 23.10 container works fine. However the 24.10 template's bridged ethernet adapter DOES NOT CONNECT.
On the host, with Ubuntu 24.10, the interface is listed as:
51: veth100i0@if2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue master vmbr0 state LOWERLAYERDOWN group default qlen 1000
link/ether <autoassigned_mac_address> brd ff:ff:ff:ff:ff:ff link-netnsid 4
On the container, the interface is listed as:
2: eth0@if51: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether <my_hardcoded_mac_address> brd ff:ff:ff:ff:ff:ff link-netnsid 0
Occasionally I've also noticed that when I create the container from my script, `master vmbr0` no longer shows up on the host and I have to manually set it. This is probably unrelated though but does signify a difference between previous behavior.
Now, here's the extra crazy bit:
If I create an Ubuntu 23.10 container and `do-release-upgrade`, it still works!
So to me, this seems to point to the fact that there is an issue with the 24.10 template's default configuration itself rather than Ubuntu 24.10/Debian 13.
Last edited: