On Mon, 2020-05-11 at 15:27 +0200, Lennart Poettering wrote:
>
> https://systemd.io/CONTAINER_INTERFACE
>
> The systemd.unified_cgroup_hierarchy=1 switch is only honoured if
> cgroupfs is not yet mounted in the container, in which case systemd
> will try to mount it. Generally, it's a good idea t
On So, 10.05.20 20:57, Mark Clarkson ([email protected]) wrote:
> Hi,
> I finally got:
>
> Failed to mount cgroup at /sys/fs/cgroup/systemd: Operation not
> permitted
> [!!] Failed to mount API filesystems, freezing.
>
> But I still can't get debug logs - any ideas?
>
> Anyway, I followed throu
On Sun, 2020-05-10 at 01:28 +0100, Mark Clarkson wrote:
>
> I would really like to get some information out of systemd to work
> through the errors, but I can't work out how to do it. I expected it
> to
> output to stdout and be accessible through 'podman logs '.
>
> I need logs!! :)
>
> Thanks!
Hi!
I have been writing a tool that creates kubernetes clusters in
containers. I had just about finished when I upgraded to Fedora 32
yesterday and it dropped docker and moved to cgroupv2.
So, I have Podman and Cgroupv2 now.
Using a centos 7 container with systemd, I cannot get systemd to start.
