Hi Michael,
I too have filed bug with lxc maintainers.
I did try to change unified to false in a Virtual Machine in Gnome
Boxes to test(*), however systemd reports only unified after change. (
output of systemd --version). I will try change it in host if it works
fine with VM.
I also did
Hi Michael,
Shouldn't "/sys/fs/cgroup/unified" be mounted by systemd to be used lxc
to use cgroupv2?
Should we need to do "mount -t tmpfs cgroup /sys/fs/cgroup" for
cgroupv2 as well? Will it be done systemd ?
In cgroupv1, it is usually seen "/sys/fs/cgroup" mounted on tmpfs. In
case of cgroupv2
Update
The /sys/fs/cgroup is not mounted after the upgrades.
After mounting it as below I am able to start the container.
mount -t tmpfs cgroup /sys/fs/cgroup
However there are errors reported.
lxc-start kan 20210126113817.580 ERRORcgfsng -
Package: systemd
Version: 247.2-5
Priority: important
Section: admin
Maintainer: Debian systemd Maintainers
Installed-Size: 16.4 MB
Pre-Depends: libblkid1 (>= 2.24), libc6 (>= 2.30), libgcrypt20 (>=
1.8.0), liblz4-1 (>= 0.0~r122), liblzma5 (>= 5.1.1alpha+20120614),
libselinux1 (>= 3.1~), libzstd1
Hi Harald,
Could you please add more information on where do you want to make this
changes?
To the GRUB of the Host?
Furthering add mount command output.
mount | grep -i "/sys/fs"
cgroup2 on /sys/fs/cgroup type cgroup2
(rw,nosuid,nodev,noexec,relatime)
pstore on /sys/fs/pstore type pstore
Package: lxc
Version: 1:4.0.5-2
I would like to file a bug for this.
The recent update of packages made lxc malfunction. Unable to start
containers.I have also noted that "Input/ouput Error" in /var/lib/lxcfs
directory. I dont think this is disk IO issue as this can reproduced. I
do have a VM
6 matches
Mail list logo