When you deploy to a container, the template container will be created first and used to clone the juju containers. Once the juju containers start, they will use the cloud-config from that file you posted in comment #8 to do some set up as part of cloud init.
That set up will configure the network, set up the system, and download and run the juju binaries. The output of those operations will be in /var/lib/juju/containers/<container-name>/console.log. It sounds like you saw there that the tools were failing to download?
If that's the case, it would be helpful to know:
- version of juju
- version of MAAS
- /etc/network/interfaces for the container that's failing to download tools
When you deploy to a container, the template container will be created first and used to clone the juju containers. Once the juju containers start, they will use the cloud-config from that file you posted in comment #8 to do some set up as part of cloud init.
That set up will configure the network, set up the system, and download and run the juju binaries. The output of those operations will be in /var/lib/ juju/containers /<container- name>/console. log. It sounds like you saw there that the tools were failing to download?
If that's the case, it would be helpful to know: interfaces for the container that's failing to download tools
- version of juju
- version of MAAS
- /etc/network/