Comment 2 for bug 1594720

I don't think our LXD code has anything to do with this and what is necessary is for the host to have the correct http and https proxies set. This should be done by our proxy updater code already.

Presumably if machine 0 needs a proxy this has already been set up in MAAS. Is that the case? Just having an APT proxy can get you a long way so it it isn't unusual to only notice problems after machine 0 seems to have bootstrapped correctly.

Can you check that on machine 0 /home/ubuntu/.juju-proxy exists and has the correct values? What does PRINTENV | grep PROXY show?