Last lxc images buggy config ?

[gvdb]

Hi to all,
I test proxmox since many month without trouble.

about new needs, i have done some test with last lxc image available from proxmox download repository.

Actually Centos 8 and Fedora 30, and the both doesn't works fine. There so buggy effects.
I don't know if it's my proxmox or the image...

Password doesn't work after clean bootup for the both. I need to reset thru 'pct xx enter'. After that works fine. Maybe post-scriting issue ?

Network setting for
- CentOS are cleanly set but not applied. DHCP seems delivered ip address. But nowhere it's setting.
- Fedora can't get config set thru proxmox gui. the ifcfg file are set by default. no ip.

So i done new CT with lxc image centos 7, and except root login, networks setting works fine.

My proxmox get last version: Linux 5.0.21-3-pve #1 SMP PVE 5.0.21-7

Anyone get the same trouble ? What the hell ?!

 

[oguz]

hi,

both templates work normally here.

can you post the container configs and pveversion -v ?

 

[gvdb]

About pve version:
proxmox-ve: 6.0-2 (running kernel: 5.0.21-3-pve)
pve-manager: 6.0-9 (running version: 6.0-9/508dcee0)
pve-kernel-5.0: 6.0-9
pve-kernel-helper: 6.0-9
pve-kernel-4.15: 5.4-6
pve-kernel-5.0.21-3-pve: 5.0.21-7
pve-kernel-5.0.21-2-pve: 5.0.21-7
pve-kernel-4.15.18-18-pve: 4.15.18-44
pve-kernel-4.15.18-9-pve: 4.15.18-30
ceph: 12.2.12-pve1
ceph-fuse: 12.2.12-pve1
corosync: 3.0.2-pve4
criu: 3.11-3
glusterfs-client: 5.5-3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.13-pve1
libpve-access-control: 6.0-2
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-5
libpve-guest-common-perl: 3.0-1
libpve-http-server-perl: 3.0-3
libpve-storage-perl: 6.0-9
libqb0: 1.0.5-1
lvm2: 2.03.02-pve3
lxc-pve: 3.1.0-65
lxcfs: 3.0.3-pve60
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.0-8
pve-cluster: 6.0-7
pve-container: 3.0-7
pve-docs: 6.0-7
pve-edk2-firmware: 2.20190614-1
pve-firewall: 4.0-7
pve-firmware: 3.0-2
pve-ha-manager: 3.0-2
pve-i18n: 2.0-3
pve-qemu-kvm: 4.0.1-3
pve-xtermjs: 3.13.2-1
qemu-server: 6.0-9
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.2-pve1

CentOS 8:
arch: amd64
cores: 1
hostname: cents8-tst
memory: 512
nameserver: 10.128.10.253
net0: name=eth0,bridge=vmbr0,gw=10.128.10.254,hwaddr=008C:69:CA:87,ip=10.128.10.51/24,ip6=auto,type=veth
ostype: centos
rootfs: lvm-datastore:vm-107-disk-0,size=8G
searchdomain: xxxxxx.intra.com
swap: 512

[root@cents8-tst ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
ONBOOT=yes
BOOTPROTO=none
IPADDR=10.128.10.51
NETMASK=255.255.255.0
GATEWAY=10.128.10.254
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6ADDR=auto

In true life, the ip is 10.128.10.28 ! DHCP address


Fedora 30:
arch: amd64
cores: 1
hostname: fedo30-tst
memory: 512
nameserver: 10.128.10.253
net0: name=eth0,bridge=vmbr0,gw=10.128.10.254,hwaddr=00:45:29:FF:36:E4,ip=10.128.10.52/24,ip6=auto,type=veth
ostype: fedora
rootfs: lvm-datastore:vm-108-disk-0,size=8G
searchdomain: xxxxx.intra.com
swap: 512

# Generated by dracut initrd
NAME="ens3"
DEVICE="ens3"
ONBOOT="yes"
NETBOOT="yes"
UUID="640ea762-2709-4c00-bab4-f7d4bdaac538"
IPV6INIT="yes"
BOOTPROTO="dhcp"
TYPE="Ethernet"
PROXY_METHOD="none"
BROWSER_ONLY="no"
DEFROUTE="yes"
IPV4_FAILURE_FATAL="no"
IPV6_AUTOCONF="yes"
IPV6_DEFROUTE="yes"
IPV6_FAILURE_FATAL="no"
IPV6_ADDR_GEN_MODE="stable-privacy"

In true life, no ip

before that, I done a clean reboot of my proxmox server. Password typed works fine after a clean LXD deployement from templates.

 

[oguz]

Fedora 30:
arch: amd64
cores: 1
hostname: fedo30-tst
memory: 512
nameserver: 10.128.10.253
net0: name=eth0,bridge=vmbr0,gw=10.128.10.254,hwaddr=00:45:29:FF:36:E4,ip=10.128.10.52/24,ip6=auto,type=veth
ostype: fedora
rootfs: lvm-datastore:vm-108-disk-0,size=8G
searchdomain: xxxxx.intra.com
swap: 512

# Generated by dracut initrd
NAME="ens3"
DEVICE="ens3"
ONBOOT="yes"
NETBOOT="yes"
UUID="640ea762-2709-4c00-bab4-f7d4bdaac538"
IPV6INIT="yes"
BOOTPROTO="dhcp"
TYPE="Ethernet"
PROXY_METHOD="none"
BROWSER_ONLY="no"
DEFROUTE="yes"
IPV4_FAILURE_FATAL="no"
IPV6_AUTOCONF="yes"
IPV6_DEFROUTE="yes"
IPV6_FAILURE_FATAL="no"
IPV6_ADDR_GEN_MODE="stable-privacy"

we use systemd-networkd for fedora. check /etc/systemd/network/ directory for PVE generated network configuration.

did you try using unprivileged containers?

 

[gvdb]

The both are unprivileged containers.

About fedora: same setting, no network up.

[Network]
Description = Interface eth0 autoconfigured by PVE
Address = 10.128.10.52/24
Gateway = 10.128.10.254
DHCP = none
IPv6AcceptRA = true

 

[oguz]

The both are unprivileged containers.

i don't see unprivileged: 1 in the configs you sent, are you sure?

About fedora: same setting, no network up.

can you try ip link set eth0 down && ip link set eth0 up in the container?

 

[gvdb]

hum .... yep, you right... well....

I created new one (Centos and Fedora)

Network works for Fedo and with good ip.

but same issue for Centos, ip from DHCP

CENTOS:

arch: amd64
cores: 1
hostname: centostest
memory: 512
nameserver: 10.128.10.xxx 10.128.10.xxx
net0: name=eth0,bridge=vmbr0,gw=10.128.10.254,hwaddr=00:A0:08:A9:xx:xx,ip=10.128.10.52/24,ip6=auto,type=veth
ostype: centos
rootfs: lvm-datastore:vm-108-disk-0,size=8G
searchdomain: xxxx.intra.com
swap: 512
unprivileged: 1

#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
valid_lft forever preferred_lft forever
41: eth0@if42: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 00:a0:08:a9:ba:a6 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet 10.128.10.21/24 brd 10.128.10.255 scope global dynamic noprefixroute eth0
valid_lft 86351sec preferred_lft 86351sec

#cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
ONBOOT=yes
BOOTPROTO=none
IPADDR=10.128.10.52
NETMASK=255.255.255.0
GATEWAY=10.128.10.254
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6ADDR=auto

 

[oguz]

hi,

i could reproduce a situation where this occurs with centos8 container. it has something to do with the ipv6 configuration (more specifically with the slaac option)

can you try setting ipv6 to dhcp or static?

 

[gvdb]

Hi
Well done !
That's it.
In static setting, i get the good IP. Strange...

 

[gvdb]

Hi to all
Issue is back since the last proxmox upgrade. (Linux 5.3.13-1-pve #1 SMP PVE 5.3.13-1 / pve-manager/6.1-3/37248ce6)

For resolving the issue, i changed LXC network settings to IPV6 to SLAAC. And removing the ifcfg-eth0 interface.
IP address is back, and no ifcfg-xxx file is present.

It's strange !

Any update about this side effect ?

 

[oguz]

hi,

Issue is back since the last proxmox upgrade. (Linux 5.3.13-1-pve #1 SMP PVE 5.3.13-1 / pve-manager/6.1-3/37248ce6)

For resolving the issue, i changed LXC network settings to IPV6 to SLAAC. And removing the ifcfg-eth0 interface.
IP address is back, and no ifcfg-xxx file is present.

thanks a lot for letting us know.

Any update about this side effect ?

sorry, this hasn't been that much of a priority with the new release. i'll try to investigate it and let you know

 

[gvdb]

Hi,
some news from new tests...
Step by step:
Starting Fedora LXC VM, no network. ip a show no nic.
Changing, without stopping the VM, the nic name from Proxmox gui web interface (from ens3 to eth0, by example): network come's up with good ip address
shuting down, and starting up the same VM; no ip
Changing, without stopping the VM, the nic name from Proxmox gui web interface (from eth0 to ens3, by example): network come's up with good ip address

Strange things !

 

[heyarray]

I'm experiencing exactly the same: after a restart of Fedora 34 LXC Containers I have to change the NIC name to an arbitrary (but different) name to get the network back up.

Kernel Version
Linux 5.4.157-1-pve #1 SMP PVE 5.4.157-1 (Mon, 29 Nov 2021 12:01:44 +0100)

PVE Manager Version
pve-manager/6.4-13/9f411e79

CT Template
fedora-34-default_20210427_amd64.tar.xz

 

[oguz]

I'm experiencing exactly the same: after a restart of Fedora 34 LXC Containers I have to change the NIC name to an arbitrary (but different) name to get the network back up.

Kernel Version
Linux 5.4.157-1-pve #1 SMP PVE 5.4.157-1 (Mon, 29 Nov 2021 12:01:44 +0100)

PVE Manager Version
pve-manager/6.4-13/9f411e79

CT Template
fedora-34-default_20210427_amd64.tar.xz

ip link set eth0 down && ip link set eth0 up doesn't work?

 

[heyarray]

Unfortunately not.