[SOLVED] No network after upgrade CT to fedora 32

frkb

Member
Oct 17, 2020
8
0
6
64
The first solution was to put a dhclient eth0 in à startup hook script (attached).

In a new container with FC32 network works.

After comparing new and old upgraded CT the fix was:
Code:
systemctl enable systemd-networkd-wait-online.service
systemctl enable systemd-networkd.service
systemctl enable systemd-networkd.socket
 

Attachments

  • guest-hookscript.txt
    2.4 KB · Views: 4
Is that an unprivileged container?
When I use Fedora 33 (new - not upgraded) the network works when using an unprivileged container.
When using privileged (which I need of course...) it's not possible to start the required services and there is no network.
 
Yes unprivileged.
On new Fedora 32 network works too. Probably also with FC 33.
Problem only appears after upgrading FC 31 to 32.
At least for me on every 6 container migrated.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!