[17:29] <jose-phillips> hi someone know how to add persist the changes on /etc/network/interfaces after add a second network interface?
[17:29] <jose-phillips> or keep the configuration on /etc/network/interfaces on  a lxc container deployed by juju
[17:54] <jose-phillips> or change the dns
[17:57] <kjackal> hi rick_h, I got  a question you might be able to help with. On a network restricted deployment we would like to have in the model cofig no-proxy a set of IPs os a few subnets. These IPs are propagated to the snapd configuration and systemd is failing to load it. https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/413
[17:57] <kjackal> Any ideas how we could work around this?
[18:12] <pmatulis> kjackal, the goal is to get the snapd system to have no_proxy declared in its /etc/environment file
[18:19] <kjackal_> pmatulis: Mostly yes. /etc/environmet should have the same line limit but I hear /etc/default/profiles/whatever.sh does not
[18:20] <kjackal_> however, i think juju is updating the snapd configuration without giving me an option.
[18:24] <kjackal_> probably related: https://bugs.launchpad.net/juju/+bug/1639494
[18:24] <mup> Bug #1639494: juju model-default no-proxy setting invalid for CIDR (172.16.0.0/16) <juju:New> <https://launchpad.net/bugs/1639494>