On Tue, Feb 18, 2020 at 09:39:14AM +0000, Laurent Bercot wrote: > In the former case, lxd *emulates* a kernel, and is supposed to adapt > to every kind of init that runs in a container, so it should follow > existing conventions and be able to adapt to every init. And that's > exactly why the lxc.signal.stop configuration switch exists!
Yes, it is. And for the most part, container creation templates should know what sort of distro, and hence init, they are setting up, so they can add the right lxc.signal.stop. But it *is* too bad that there is no way really to query "hey, for this init that's running in this container, what *should* I send it?" I suspect that's where some users get annoyed. If you're creating and destroying a lot containers with a lot if different distros, I can see where having to guess this for yourself can be a bit of a blocker. So since you can't query, a convention would be nice. But that ship too has sailed. -serge
