On 2018-05-03 21:57, Fajar A. Nugraha wrote:
I can confirm this. Seeing the same issue.
BTW. It's the /etc/netplan/10-lxc.yaml
Not working (current) version:
network:
ethernets:
eth0: {dhcp4: true}
version: 2
Working version (for me):
network:
version: 2
ethernets:
eth0:
dhcp4: true
Works for me. Both with images:ubuntu/bionic (which has
/etc/netplan/10-lxc.yaml, identical to your 'not working' one) and
ubuntu:bionic (which has /etc/netplan/50-cloud-init.yaml).
Then again the images:ubuntu/bionic one has '20180503_11:06' in its
description, so it's possible that the bug was fixed recently.
Indeed, the bug seems now fixed in the bionic image and new containers
are getting IPv4 via DHCP again:
| | 88a22ac497ad | no | Ubuntu bionic amd64 (20180503_03:49)
| x86_64 | 104.71MB | May 3, 2018 at 8:51am (UTC) |
This one was producing broken /etc/netplan/10-lxc.yaml:
| | 87b5c0fec8ff | no | Ubuntu bionic amd64 (20180502_09:49) |
x86_64 | 118.15MB | May 3, 2018 at 2:39am (UTC) |
Tomasz Chmielewski
https://lxadm.com
_______________________________________________
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users
