On 04/27/2018 11:41 AM, Lennart Poettering wrote:
On Fr, 27.04.18 17:27, Pavel Raiskup (praiskup@xxxxxxxxxx) wrote:
Hi all,
just wanted to let you know about trivial experiment [1] with systemd in
container. Non-privileged systemd can now pretty fine run in docker
container (tested on Fedora 27 box).
Hmm, IIRC there were at least two isues still, did they get resolved?
Specifically:
1. docker fakes a /dev/console that doesn't behave like a console
usually works, i.e. if a hangup is seen on it then it will destroy
the pty behind it, instead of keeping it around...
First off this is not a Docker issue, it is a runc and OCI Runtime
issue. I am not sure if this is fixed or not at this point.
2. docker sends SIGTERM to the container's PID 1 when it wants it to
go down even though SIGTERM to PID 1 on SysV systems generally
means "please reexecute", and not "please shut down".
The container runtimes can specify a stop signal, so as long as you
specify the correct stop signal when creating your systemd based image,
everything should work properly.
NOTE you need to have oci-systemd-hook installed, and the container
runtime needs to be able support OCI Runtime hooks.
podman, CRI-O and ProjectAtomic/Docker all support them. Upstream
Docker does NOT.
What's the current state on that?
Lennart
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
