On Thu, 30.04.15 10:01, arnaud gaboury ([email protected]) wrote: > I used to boot the container this way : > # systemd-nspawn --network-bridge=br0 -bD /path_to/my_container > > Is this correct?
Looks fine. > > > ***************** > Now on the container side: > > Nothing configured. NetworkManager enabled, systemd-networkd enabled > and started. NM doesn't really support being run in a container. > ------------------------------- > $ ip a > 2: host0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group > default qlen 1000 > link/ether 0e:7f:c3:fb:25:b1 brd ff:ff:ff:ff:ff:ff > ------------------------------------- > host0 is down Please check what "networkctl status -a" in the container shows. It should tell you whether networkd is configured to do anything. Also, what does "journalctl -u systemd-networkd -n 200" show in the container? Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
