Bug 76192 - systemd-nspawn/networkd: Networking does not work when using --network-bridge
Summary: systemd-nspawn/networkd: Networking does not work when using --network-bridge
Status: RESOLVED FIXED
Alias: None
Product: systemd
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: systemd-bugs
QA Contact: systemd-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-15 08:12 UTC by Tobias Hunger
Modified: 2019-11-12 18:48 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Tobias Hunger 2014-03-15 08:12:37 UTC 
Could you please bring up the interfaces you create and add to bridges? That would make systemd-nspawn work out of the box for me.

Details of what I did:

I am trying to run a container like this:
systemd-nspawn --directory=/vms/test --boot --network-bridge=br0 --machine=test

The container starts fine and I can login there.

Running "ip addr" in the container shows host0 to be there but without carrier.

Some poking around the host shows that vb-test is there and is set up as part of br0. "ip addr" claims that the link is down. Running "ip link set dev vb-test up" on the host brings that link up. Inside the container host0 now got its carrier and it can go out via DHCP to retrieve its IP (once networkd is started in the container).
Comment 1 Lennart Poettering 2014-03-17 00:21:43 UTC 
Fixed in git.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.