I can confirm that the updated packages resolved the issue in my case, in a precise container.
Chroot wouldn't let me use the host network, so I configured network manually in the container: sudo ifconfig eth0 10.0.3.100 (for ex.) sudo route add default gw 10.0.3.1 sudo echo "nameserver 10.0.3.1" > /etc/resolv.conf Then apt let's you do the rest. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1236490 Title: Container has no networking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1236490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
