Comment 49 for bug 1633788

> No, I mean, I just though that juju would try to contact the container throught its IP on the bridge range, which in my case would have been 10.131.62.135:8443 instead of 10.131.62.1:8443.

Just to make sure we're both on the same page: it's happening the other way around. The container (.135) needs to contact the host (.1). Think of the host as the "cloud" API endpoint, with which the Juju controller (running in a container) communicates.

The command that Juju runs at bootstrap time, inside the container, is:
    /var/lib/juju/tools/2.1.1-xenial-amd64/jujud bootstrap-state --timeout 20m0s --data-dir /var/lib/juju --debug /var/lib/juju/bootstrap-params

You could also just try "curl -k https://10.131.62.1:8443" from inside the container. If that doesn't work, then something is screwy with the networking/firewalling.

I've tried making my LXD network configuration the same as yours, but still it all works for me.