Kinda hard to tell what's going on exactly, I can think of one of two things: - You didn't run "lxd init" or "dpkg-reconfigure lxd" and your lxdbr0 bridge doesn't provide the containers with an IP address. Though I believe Juju is supposed to detect this case and refuse to run. - Your container has working networking but didn't get the proxy setting. I seem to remember you mentioning that you set the environment.http_proxy and environment.https_proxy keys, note that those DO NOT apply for things using ssh to enter the container, such as Juju. That's because the init systems do not propagate the environment they receive down to their children... LXD works around that by manually re-setting those keys on "lxc exec" but that won't do you any good when sshing into the container.
There may be a way to tell Juju about the proxy, if not, you may be able to tell cloud-init about it by setting the "user.vendor-data" key in a profile Juju uses (most likely the "default" profile). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575386 Title: Proxy issue with 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1575386/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
