units: order nspawn containers after network.target
authorLennart Poettering <lennart@poettering.net>
Mon, 11 May 2015 20:08:28 +0000 (22:08 +0200)
committerLennart Poettering <lennart@poettering.net>
Mon, 11 May 2015 20:18:20 +0000 (22:18 +0200)
commitd3650f0c4b04990c5b9e8a3463de309ec165fcf5
tree457f4f0162d2e70a99a236224a0cc1b13038df02
parent4b64536ee7fd0438c93d1784824098f826cd642c
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