[systemd-bugs] [Bug 76192] New: systemd-nspawn/networkd: Networking does not work when using --network-bridge

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sat Mar 15 01:12:37 PDT 2014


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

          Priority: medium
            Bug ID: 76192
          Assignee: systemd-bugs at lists.freedesktop.org
           Summary: systemd-nspawn/networkd: Networking does not work when
                    using --network-bridge
        QA Contact: systemd-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: tobias.hunger at gmail.com
          Hardware: Other
            Status: NEW
           Version: unspecified
         Component: general
           Product: systemd

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).

-- 
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/20140315/0a31fe06/attachment.html>


More information about the systemd-bugs mailing list