Hi, Thanks for the bug report. rkt is supposed to work with cgroup-v2 since v1.16.
I forwarded this bug upstream: https://github.com/rkt/rkt/issues/3741 On Fri, Jul 7, 2017 at 11:56 AM, Valentin Vidic <valentin.vi...@carnet.hr> wrote: > Package: rkt > Version: 1.21.0+dfsg-1+b1 > Severity: important > > Dear Maintainer, > > It seems starting a container does now work with systemd 233 anymore: > > # rkt run coreos.com/etcd:v3.1.7 > stage1: warning: no volume specified for mount point "data-dir", implicitly > creating an "empty" volume. This volume will be removed when the pod is > garbage-collected. > stage1: warning: no volume specified for mount point "data-dir", implicitly > creating an "empty" volume. This volume will be removed when the pod is > garbage-collected. > Failed to mount cgroup2 on > /var/lib/rkt/pods/run/25a3fe1c-0e21-49a0-9988-a951fc8aced0/stage1/rootfs/sys/fs/cgroup/unified > (MS_NOSUID|MS_NODEV|MS_NOEXEC ""): No such file or directory > > This is probably related to the new /sys/fs/cgroup/unified directory > that rkt does not handle properly. Booting with the parameter > > systemd.legacy_systemd_cgroup_controller > > restores the original cgroup behaviour and rkt run works again. > > Perhaps newer versions of rkt support unified cgroups? > > > -- System Information: > Debian Release: buster/sid > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.11.0-1-amd64 (SMP w/8 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), > LANGUAGE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/bash > Init: systemd (via /run/systemd/system) > > Versions of packages rkt depends on: > ii adduser 3.115 > ii dbus 1.10.20-1 > ii libc6 2.24-12 > ii systemd 233-10 > ii systemd-container 233-10 > > rkt recommends no packages. > > Versions of packages rkt suggests: > pn docker2aci <none> > > -- no debconf information >
