Comment 0 for bug 906500

I encountered this problem when trying to contain lxc containers after my first one. The host had full access to archive.ubuntu.com, as verified by Serge Hallyn and Robert Collins via various diagnostics.

After trying more careful approaches to a solution, Serge Hallyn recommended that we just wipe out the lxc cache. "rm -rf /var/cache/lxc/*". This solved the problem.

I noticed that switching networks seems to trigger the problem. If I create a container at home, and then go to a co-working spot and try to make a new one, I get this error. Then I clear out the cache as Serge described, and I can create a new container. A subsequent attempt, also at the co-working spot, also succeeds.

However, when I go back home, and then try to make a container, I get this error again. I clear out the cache, and I can make a new container, and then another one.

Maybe the network correlation is coincidental, but it seems to be valid in my experiences so far.

This is on an Oneiric host, making Lucid containers.