summaryrefslogtreecommitdiff
path: root/units/systemd-nspawn@.service.in
diff options
context:
space:
mode:
authorLennart Poettering <lennart@poettering.net>2015-05-11 22:08:28 +0200
committerLennart Poettering <lennart@poettering.net>2015-05-11 22:18:20 +0200
commitd3650f0c4b04990c5b9e8a3463de309ec165fcf5 (patch)
tree457f4f0162d2e70a99a236224a0cc1b13038df02 /units/systemd-nspawn@.service.in
parent4b64536ee7fd0438c93d1784824098f826cd642c (diff)
downloadsystemd-d3650f0c4b04990c5b9e8a3463de309ec165fcf5.tar.gz
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.
Diffstat (limited to 'units/systemd-nspawn@.service.in')
-rw-r--r--units/systemd-nspawn@.service.in1
1 files changed, 1 insertions, 0 deletions
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