On Thu, May 3, 2018 at 1:28 PM, Kees Bos <cornelis....@gmail.com> wrote: > On Thu, 2018-05-03 at 08:09 +0200, Kees Bos wrote: >> On Thu, 2018-05-03 at 12:58 +0900, Tomasz Chmielewski wrote: >> > >> > Reproducing is easy: >> > >> > # lxc launch images:ubuntu/bionic/amd64 bionic-broken-dhcp >> > >> > >> > Then wait a few secs until it starts - "lxc list" will show it has >> > IPv6 >> > address (if your bridge was configured to provide IPv6), but not >> > IPv4 >> > (and you can confirm by doing "lxc shell", too): >> > >> > # lxc list >> > >> > >> >> 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. -- Fajar _______________________________________________ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users