Thanks for the clue. Looking into this.
Jake
On Sat, Apr 14, 2018 at 10:31 AM, Sergiusz Pawlowicz <
sergi...@pawlowicz.name> wrote:
> it's not a bug, it is a feature
>
> man netplan
> ___
> lxc-users mailing list
> lxc-users@lists.linuxcontainers.org
>
it's not a bug, it is a feature
man netplan
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users
Bump -
The bug is 100% repeatable. Steps to reproduce:
1. create ubuntu container (lxc launch)
2. enter container and configure a static IP in /etc/network/interfaces
3. If container is 16.04, only static IP exists. if container is 18.04.
there are both static and dhcp ips.
+-+--
Thanks Simos,
The host has a bridge, br0, but not an lxc-specific one
(USE_LXC_BRIDGE="false" in /etc/default/lxc-net)
The 192.168.111 range is from the pool on the local dhcp box. However, this
container is configured to use a static IP in /etc/network/interfaces:
--
# interfaces(5) file used by
These 192.168.111.x IP addresses are not LXD default private IP addresses.
Have you configured a bridge or a macvlan?
Simos
On Sat, Apr 7, 2018 at 11:16 PM, jjs - mainphrame wrote:
> Greetings,
>
> Running lxd-3.0.0 on ubuntu 18.04 beta
>
> I've set up a couple of new 16.04 cts and they act as I
Greetings,
Running lxd-3.0.0 on ubuntu 18.04 beta
I've set up a couple of new 16.04 cts and they act as I expect.
I set up an 18.04 ct and a persistent unwanted dhcp IP appears in the lxc
list:
root@ronnie:~# lxc list
+---+-++--++-