Can't deploy service in a freshly-bootstrapped LXC environment

I just found some failure messages in /var/log/cloud-init{,-output}.log inside the LXC container. I don't know if anything here is pertinent.

David, I found my first attempts at juju deployment failed with the same error message you have; thanks for giving the /var/log/cloud-init-output.log name within the container, that was sufficient for me to determine that my apt-cacher-ng was not yet configured to listen on the rfc1918 IP address that LXC or Juju configured for me.

Your log file shows similar failures to retrieve packages; it looks to me like your local package mirror is broken or out of date or similarly busted.

Hope this helps.

I don't think there's a problem with the address that apt-cacher-ng is listening on. After purging apt-cacher-ng and reinstalling, I see that the LXC container is able to fetch index files through the cache, but then there are size mismatches on basically every deb file.

Besides what may or may not be wrong with apt-cacher-ng, juju should not lose track of an instance in this way; it should detect that the instance has failed in someway and report that to the user.

Tried clearing the cache *and* disabling ufw, as described in http://askubuntu.com/questions/134977/juju-stuck-in-pending-state-when-using-lxc . No luck.