Thanks - then while we could call this a fixed kernel bug, it's not an
lxc bug.
** Changed in: lxc (Ubuntu)
Status: Incomplete => Invalid
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Fix Released
--
You r
Yes, this workaround fixed the issue for me.
--
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.laun
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"
Hi,
so just to be sure, did that actually fix this bug for you? Or are you
still having trouble?
** Changed in: lxc (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Stephane Graber explains:
bug 1236490 very much looks like isc-dhcp-* is out of date in your container
a kernel change in 3.10 caused veth devices to do udp offloading which wasn't
supported by the isc-dhcp we shipped in precise, quantal and raring
so I SRUed the fix a couple months back to all
