Support for Ubuntu 17.10/Netplan
- Thread starter blueberry
- Start date
+1 to this. I've not been able to get an Artful LXC container with working networking up under Proxmox 5.0/5.1.
@blueberry, how did you get networking functioning?
@blueberry, how did you get networking functioning?
Bump on this one. has anyone else gotten networking functional with an Ubuntu Artful/17.10 LXC container? I've tried a few different configurations of Network Manager / Netplan / systemd-networkd but can't get it going. It doesn't seem to matter whether the container is privileged or not, nor does it matter if IPv4 is set to static or DHCP in the container config.
Thanks.
Thanks.
i tested a bit today, and afaics, the upstream lxc template has a default netplan config for eth0 (dhcp), and it does not use the /etc/network/interfaces anymore
i sent a patch, so that we use systemd-networkd for ubuntu >= 17.10
(https://pve.proxmox.com/pipermail/pve-devel/2017-October/029283.html)
i sent a patch, so that we use systemd-networkd for ubuntu >= 17.10
(https://pve.proxmox.com/pipermail/pve-devel/2017-October/029283.html)
When using the Ubuntu 17.10 template on LXC you will not be able to configure network from proxmox and get network working that way.
Code:
proxmox-ve: 4.4-107 (running kernel: 4.4.98-6-pve)
pve-manager: 4.4-22 (running version: 4.4-22/2728f613)
pve-kernel-4.4.98-6-pve: 4.4.98-107
lvm2: 2.02.116-pve3
corosync-pve: 2.4.2-2~pve4+1
libqb0: 1.0.1-1
pve-cluster: 4.0-54
qemu-server: 4.0-115
pve-firmware: 1.1-11
libpve-common-perl: 4.0-96
libpve-access-control: 4.0-23
libpve-storage-perl: 4.0-76
pve-libspice-server1: 0.12.8-2
vncterm: 1.3-2
pve-docs: 4.4-4
pve-qemu-kvm: 2.9.1-6~pve4
pve-container: 1.0-104
pve-firewall: 2.0-33
pve-ha-manager: 1.0-41
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u3
lxc-pve: 2.0.7-4
lxcfs: 2.0.6-pve1
criu: 1.6.0-1
novnc-pve: 0.5-9
smartmontools: 6.5+svn4324-1~pve80
OK, a network setup fix for 17.10 was only applied to PVE 5 but not backported to PVE 4...
I'll send a patch, maybe we still get it into PVE 4.4 as it could really count as essential bug fix for 17.10...
I'll send a patch, maybe we still get it into PVE 4.4 as it could really count as essential bug fix for 17.10...