<div dir="ltr">Thanks for the additional info and pointers. <br><br>BTW I'd noticed that the ip command showed the extraneous IP missed by ifconfig. But not showing the extra IP was not the problem, rather that the extra IP existed at all. In any event, the removal of netplan and cloud packages facilitate the intended modes of operation in my environment (system type containers using bridged networking and static IPs)<br><br>But I do prefer to see the whole system work as intended, so thanks for the netplan details.<br><br>BTW - re your recommendation to install LXD via snap - is the preferred install method moving forward? <br><div><br></div><div>Jake</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Apr 19, 2018 at 8:13 AM, David Favor <span dir="ltr"><<a href="mailto:david@davidfavor.com" target="_blank">david@davidfavor.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">jjs - mainphrame wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks for the insights. The netplan and cloud packages look like something which might be indeed useful in uses cases other than mine.<br>
In retrospect I'm curious how 16.04 is working so well without netplan. Apparently further study is needed...<br>
</blockquote>
<br></span>
Netplan support begins with Artful (where Netplan + old style EIN coexist).<br>
<br>
Netplan is default in Bionic... well sort of default Artful too.<br>
<br>
My suggestion is when Bionic releases in a few days, start with a fresh system.<br>
<br>
1) Install Bionic from scratch at machine level. No update, true install.<br>
<br>
2) Install LXD via snap. No migration, true install.<br>
<br>
3) Do an lxd copy remote:cname local:cname for each container, to move them<br>
from where ever they live to your Bionic machine.<br>
<br>
The /etc/netplan/60-public-init.ya<wbr>ml file format I've been using, which works...<br>
<br>
network:<br>
version: 2<br>
ethernets:<br>
eth0:<br>
match:<br>
name: eth0<br>
addresses:<br>
- X.X.X.X/32<br>
<br>
The Netplan docs are... to me... are overly complex + difficult to understand.<br>
<br>
For example, the eth0: above requires the match: operator (I guess) to differentiate<br>
between base interface name + aliases.<br>
<br>
Just start with the above Netplan config file + get your system working, then start<br>
making whatever experimental changes seem useful.<br>
<br>
Netplan is very unforgiving + in many cases syntax errors emit no errors/warnings,<br>
so you have to do eyeball syntax checking.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Jake<span class=""><br>
<br>
On Mon, Apr 16, 2018 at 6:13 AM, David Favor <<a href="mailto:david@davidfavor.com" target="_blank">david@davidfavor.com</a> <mailto:<a href="mailto:david@davidfavor.com" target="_blank">david@davidfavor.com</a>>> wrote:<br>
<br>
jjs - mainphrame wrote:<br>
<br>
Confirmed, removing netplan solves the problem.<br>
<br>
Thanks for the hint.<br>
<br>
Jake<br>
<br>
On Sat, Apr 14, 2018 at 10:39 AM, jjs - mainphrame<br>
<<a href="mailto:jjs@mainphrame.com" target="_blank">jjs@mainphrame.com</a> <mailto:<a href="mailto:jjs@mainphrame.com" target="_blank">jjs@mainphrame.com</a>><br></span><span class="">
<mailto:<a href="mailto:jjs@mainphrame.com" target="_blank">jjs@mainphrame.com</a> <mailto:<a href="mailto:jjs@mainphrame.com" target="_blank">jjs@mainphrame.com</a>>>> wrote:<br>
<br>
Thanks for the clue. Looking into this.<br>
<br>
Jake<br>
<br>
On Sat, Apr 14, 2018 at 10:31 AM, Sergiusz Pawlowicz<br>
<<a href="mailto:sergiusz@pawlowicz.name" target="_blank">sergiusz@pawlowicz.name</a> <mailto:<a href="mailto:sergiusz@pawlowicz.name" target="_blank">sergiusz@pawlowicz.nam<wbr>e</a>><br></span>
<mailto:<a href="mailto:sergiusz@pawlowicz.name" target="_blank">sergiusz@pawlowicz.nam<wbr>e</a><span class=""><br>
<mailto:<a href="mailto:sergiusz@pawlowicz.name" target="_blank">sergiusz@pawlowicz.nam<wbr>e</a>>>> wrote:<br>
<br>
it's not a bug, it is a feature<br>
<br>
man netplan<br>
<br>
<br>
Netplan doesn't get rid of the "pesky DHCP IP".<br>
<br>
Currently there's a bug in ifconfig, which fails to report the DHCP IP.<br>
<br>
The only way (till the ifconfig bug is fixed) you can view all IPs<br>
via...<br>
<br>
ip addresses (container level)<br>
<br>
lxc list (machine level)<br>
<br>
Likely good for you to read many posts about the purpose of the DHCP IP<br>
inside containers.<br>
<br>
If you do destroy this IP (in netplan - rm -f /etc/netplan/50*), then<br>
you'll produces subtle packet routing breakage when trying to<br>
communicate<br>
between containers (yes even if they have public IPs).<br>
<br>
______________________________<wbr>_________________<br>
lxc-users mailing list<br>
<a href="mailto:lxc-users@lists.linuxcontainers.org" target="_blank">lxc-users@lists.linuxcontainer<wbr>s.org</a><br></span>
<mailto:<a href="mailto:lxc-users@lists.linuxcontainers.org" target="_blank">lxc-users@lists.linuxc<wbr>ontainers.org</a>><br>
<a href="http://lists.linuxcontainers.org/listinfo/lxc-users" rel="noreferrer" target="_blank">http://lists.linuxcontainers.o<wbr>rg/listinfo/lxc-users</a><br>
<<a href="http://lists.linuxcontainers.org/listinfo/lxc-users" rel="noreferrer" target="_blank">http://lists.linuxcontainers.<wbr>org/listinfo/lxc-users</a>><br>
<br>
<br>
<br>
------------------------------<wbr>------------------------------<wbr>------------<span class=""><br>
<br>
______________________________<wbr>_________________<br>
lxc-users mailing list<br>
<a href="mailto:lxc-users@lists.linuxcontainers.org" target="_blank">lxc-users@lists.linuxcontainer<wbr>s.org</a><br>
<a href="http://lists.linuxcontainers.org/listinfo/lxc-users" rel="noreferrer" target="_blank">http://lists.linuxcontainers.o<wbr>rg/listinfo/lxc-users</a><br>
</span></blockquote><div class="HOEnZb"><div class="h5">
______________________________<wbr>_________________<br>
lxc-users mailing list<br>
<a href="mailto:lxc-users@lists.linuxcontainers.org" target="_blank">lxc-users@lists.linuxcontainer<wbr>s.org</a><br>
<a href="http://lists.linuxcontainers.org/listinfo/lxc-users" rel="noreferrer" target="_blank">http://lists.linuxcontainers.o<wbr>rg/listinfo/lxc-users</a></div></div></blockquote></div><br></div>