Thanks for the insights. The netplan and cloud packages look like something
which might be indeed useful in uses cases other than mine.
In retrospect I'm curious how 16.04 is working so well without netplan.
Apparently further study is needed...

Jake

On Mon, Apr 16, 2018 at 6:13 AM, David Favor <da...@davidfavor.com> wrote:

> jjs - mainphrame wrote:
>
>> Confirmed, removing netplan solves the problem.
>>
>> Thanks for the hint.
>>
>> Jake
>>
>> On Sat, Apr 14, 2018 at 10:39 AM, jjs - mainphrame <j...@mainphrame.com
>> <mailto:j...@mainphrame.com>> wrote:
>>
>>     Thanks for the clue. Looking into this.
>>
>>     Jake
>>
>>     On Sat, Apr 14, 2018 at 10:31 AM, Sergiusz Pawlowicz
>>     <sergi...@pawlowicz.name <mailto:sergi...@pawlowicz.name>> wrote:
>>
>>         it's not a bug, it is a feature
>>
>>         man netplan
>>
>
> Netplan doesn't get rid of the "pesky DHCP IP".
>
> Currently there's a bug in ifconfig, which fails to report the DHCP IP.
>
> The only way (till the ifconfig bug is fixed) you can view all IPs via...
>
>    ip addresses (container level)
>
>    lxc list     (machine level)
>
> Likely good for you to read many posts about the purpose of the DHCP IP
> inside containers.
>
> If you do destroy this IP (in netplan - rm -f /etc/netplan/50*), then
> you'll produces subtle packet routing breakage when trying to communicate
> between containers (yes even if they have public IPs).
>
> _______________________________________________
> lxc-users mailing list
> lxc-users@lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-users
>
_______________________________________________
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Reply via email to