On Thu, Dec 17, 2015 at 11:20 AM, Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> wrote: > On Thu, Dec 17, 2015 at 11:07:34AM -0500, Colin Walters wrote: >> Let's be clear - from my perspective systemd's design is awesome >> for the *real* pid 1. AFAIK no one here is talking about changing anything >> related to that. We're just talking about supporting microservice >> containers without a pid 1 in the container namespace. > > I agree here as well. And, in fact, I'd like systemd to be the number 1 > and primary choice for containers which _do_ need process management. > As it stands now, we are in real danger of losing that. Docker > recommends Supervisor. I know people are all excited about S6. And > there's good ol' Runit. > > > -- > Matthew Miller > <mattdm@xxxxxxxxxxxxxxxxx> > Fedora Project Leader > -- > devel mailing list > devel@xxxxxxxxxxxxxxxxxxxxxxx > http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx It doesn't help that there doesn't seem to be a way to use systemd's own container technologies to do these things in a more lightweight, yet compatible fashion. nspawn currently only does OS style containers, where you have another PID 1 inside. If something that leveraged systemd as the service manager existed that also allowed microservices to work very well, then you've got a recipe for some interesting solutions. -- 真実はいつも一つ！/ Always, there's only one truth! -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
