From dec718065b59babdbc502e87149c310a7a297172 Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Thu, 16 Feb 2017 17:57:30 +0100 Subject: units: order systemd-nspawn@.service after systemd-resolved.service This way, the nspawn internal check whether resolved is running will succeed if it is enabled. Fixes: #4649 --- units/systemd-nspawn@.service.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'units/systemd-nspawn@.service.in') diff --git a/units/systemd-nspawn@.service.in b/units/systemd-nspawn@.service.in index e8d1fff7ab..8c0685aef5 100644 --- a/units/systemd-nspawn@.service.in +++ b/units/systemd-nspawn@.service.in @@ -10,7 +10,7 @@ Description=Container %i Documentation=man:systemd-nspawn(1) PartOf=machines.target Before=machines.target -After=network.target +After=network.target systemd-resolved.service [Service] ExecStart=@bindir@/systemd-nspawn --quiet --keep-unit --boot --link-journal=try-guest --network-veth -U --settings=override --machine=%i -- cgit v1.2.3-54-g00ecf