Following 'setenforce 0' I still see the same issue (I was also suspecting SELinux!).
A few additional data points:
- this was not seen when using systemd v230 inside the container
- this is also seen on CentOS 8.4
- this is seen under docker even if the container's cgroup driver is changed from 'cgroupfs' to 'systemd'
Thanks,
Lewis
On Tue, 10 Jan 2023 at 11:12, Lennart Poettering <lennart@xxxxxxxxxxxxxx> wrote:
On Mo, 09.01.23 19:45, Lewis Gaul (lewis.gaul@xxxxxxxxx) wrote:
> Hi all,
>
> I've come across an issue when restarting a systemd container, which I'm
> seeing on a CentOS 8.2 VM but not able to reproduce on an Ubuntu 20.04 VM
> (both cgroups v1).
selinux?
Lennart
--
Lennart Poettering, Berlin
