From d3650f0c4b04990c5b9e8a3463de309ec165fcf5 Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Mon, 11 May 2015 22:08:28 +0200 Subject: units: order nspawn containers after network.target This way we know that any bridges and other user-created network devices are in place, and can be properly added to the container. In the long run this should be dropped, and replaced by direct calls inside nspawn that cause the devices to be created when necessary. --- units/systemd-nspawn@.service.in | 1 + 1 file changed, 1 insertion(+) (limited to 'units') diff --git a/units/systemd-nspawn@.service.in b/units/systemd-nspawn@.service.in index 6bfa55ac37..9492c8c0f8 100644 --- a/units/systemd-nspawn@.service.in +++ b/units/systemd-nspawn@.service.in @@ -10,6 +10,7 @@ Description=Container %I Documentation=man:systemd-nspawn(1) PartOf=machines.target Before=machines.target +After=network.target [Service] ExecStart=@bindir@/systemd-nspawn --quiet --keep-unit --boot --link-journal=try-guest --network-veth --machine=%I -- cgit v1.2.3-54-g00ecf