Re: [systemd-devel] Waiting for nspawn services

2014-10-27 Thread Lennart Poettering
On Sat, 25.10.14 05:39, Rich Freeman (r-syst...@thefreemanclan.net) wrote: One of the useful options in nspawn is the ability to boot the init within the container using -b, especially if that init happens to be systemd. However, I could not find any easy way to set a dependency on a

Re: [systemd-devel] Waiting for nspawn services

2014-10-27 Thread Rich Freeman
On Mon, Oct 27, 2014 at 10:49 AM, Lennart Poettering lenn...@poettering.net wrote: In general I think making use of socket notification here would be the much better option, as it removes the entire need for ordering things here. nspawn already support socket activation just fine. If your

Re: [systemd-devel] Waiting for nspawn services

2014-10-27 Thread Lennart Poettering
On Mon, 27.10.14 11:24, Rich Freeman (r-syst...@thefreemanclan.net) wrote: On Mon, Oct 27, 2014 at 10:49 AM, Lennart Poettering lenn...@poettering.net wrote: In general I think making use of socket notification here would be the much better option, as it removes the entire need for ordering

Re: [systemd-devel] Waiting for nspawn services

2014-10-27 Thread Reindl Harald
Am 27.10.2014 um 16:32 schrieb Lennart Poettering: (Note though that ymmv on this, because depending on the software you use it might want to reverse-dns lookup incomoing connections, and that would fail if the container doesn't have network access to do DNS... That said, if mysql would do

Re: [systemd-devel] Waiting for nspawn services

2014-10-27 Thread Rich Freeman
On Mon, Oct 27, 2014 at 11:32 AM, Lennart Poettering lenn...@poettering.net wrote: Network namespaces are relevant for the process that originally binds the sockets. In the case of socket-activated containers that would be the host. If you then pass the fds into the containers and those are

Re: [systemd-devel] Waiting for nspawn services

2014-10-27 Thread Lennart Poettering
On Mon, 27.10.14 11:49, Rich Freeman (r-syst...@thefreemanclan.net) wrote: On Mon, Oct 27, 2014 at 11:32 AM, Lennart Poettering lenn...@poettering.net wrote: Network namespaces are relevant for the process that originally binds the sockets. In the case of socket-activated containers that

[systemd-devel] Waiting for nspawn services

2014-10-25 Thread Rich Freeman
One of the useful options in nspawn is the ability to boot the init within the container using -b, especially if that init happens to be systemd. However, I could not find any easy way to set a dependency on a service within a container. Example use case: Unit 1 boots an nspawn container that

Re: [systemd-devel] Waiting for nspawn services

2014-10-25 Thread Zbigniew Jędrzejewski-Szmek
On Sat, Oct 25, 2014 at 05:39:51AM -0400, Rich Freeman wrote: One of the useful options in nspawn is the ability to boot the init within the container using -b, especially if that init happens to be systemd. However, I could not find any easy way to set a dependency on a service within a