[systemd-bugs] [Bug 85464] systemd-nspawn --network-bridge breaks networking in container's host

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=85464

--- Comment #4 from Ed Tomlinson <edt at aei.ca> ---
Leo,

The 169.x.x.x and dhcp get assigned due to the stuff in
/usr/lib/systemd/network which I have disabled in the container and kvm - I
want static assignments.  There are three systems involved

physical grover <-> kvm host <-> nspawn dev

where grover runs the kvm called host and the kvm runs the nspawned container
dev

The problem with non root users (using ssh) occurs between the users in grover
and users in the kvm when the nspawned container is active using
network-bridge, network-veth or network-interface (I did not test just
private-network).  It does not mater if the network between host and dev is
configured or not.  Just starting dev breaks the network between grover and
host which is NOT nice at all.

Before it gets asked I have tried this with and without firewalls enabled

Ed

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20141026/264ebdd8/attachment.html>