On Fr, 29.09.23 10:53, Lewis Gaul (lewis.g...@gmail.com) wrote:
> Hi systemd team,
>
> I've encountered an issue when running systemd inside a container using
> cgroups v2, where if a container exec process is created at the wrong
> moment during early startup then systemd will fail to move all pr
> Wouldn't it be better to have the container inform the host via
NOTIFY_SOCKET (the Type=notify mechanism)? I believe systemd has had
support for sending readiness notifications from init to a container
manager for quite a while.
> Use the notify socket and you'll get a notification back when th
On Fri, 29 Sept 2023 at 12:00, Lewis Gaul wrote:
>
> Hi systemd team,
>
> I've encountered an issue when running systemd inside a container using
> cgroups v2, where if a container exec process is created at the wrong moment
> during early startup then systemd will fail to move all processes int
On Fri, Sep 29, 2023, 12:54 Lewis Gaul wrote:
> Hi systemd team,
>
> I've encountered an issue when running systemd inside a container using
> cgroups v2, where if a container exec process is created at the wrong
> moment during early startup then systemd will fail to move all processes
> into a
