Public bug reported: I encountered this problem when trying to create 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. ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Description changed: - 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. + I encountered this problem when trying to create 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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/906500 Title: lxc-create fails with errors that it is unable to access archive.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/906500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs