From: Lennart Poettering <lennart@poettering.net>
Date: Mon, 11 May 2015 20:08:28 +0000 (+0200)
Subject: units: order nspawn containers after network.target
X-Git-Tag: v220~167
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=d3650f0c4b04990c5b9e8a3463de309ec165fcf5;p=thirdparty%2Fsystemd.git

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

diff --git a/units/systemd-nspawn@.service.in b/units/systemd-nspawn@.service.in
index 6bfa55ac375..9492c8c0f8b 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