Your message dated Thu, 2 Jan 2020 22:26:36 +0900
with message-id
<camygc7bcfdkahxc7hrkslhkqx1es90vtlb7bmwkuqhctnix...@mail.gmail.com>
and subject line Re: lxc: non-root user cannot start a container under cgroupv2
/ unified hierarchy
has caused the Debian Bug report #946480,
regarding lxc: non-root user cannot start a container under cgroupv2 / unified
hierarchy
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
946480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946480
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: lxc
Version: 1:3.1.0+really3.0.4-2
Severity: important
Tags: upstream
User: [email protected]
Usertags: cgroupv2
Control: forwarded -1 https://github.com/lxc/lxc/issues/3221
Control: block 943981 by -1
Dear Maintainer,
Exactly the same as reported by a Fedora 31 user at
https://github.com/lxc/lxc/issues/3221
I believe that this is not a duplicate of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888647
because libpam-cgfs can do nothing useful under cgroupv2 / unified hierarchy
as discussed at https://github.com/lxc/lxc/issues/3198
Best regards, Ryutaroh
-- System Information:
Debian Release: 10.1
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'unstable'),
(500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8),
LANGUAGE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages lxc depends on:
ii debconf [debconf-2.0] 1.5.71
ii libc6 2.29-2
ii libgcc1 1:8.3.0-6
ii liblxc1 1:3.1.0+really3.0.4-2
ii lsb-base 10.2019051400
Versions of packages lxc recommends:
ii apparmor 2.13.2-10
pn bridge-utils <none>
ii debootstrap 1.0.114
ii dirmngr 2.2.12-1+deb10u1
ii dnsmasq-base [dnsmasq-base] 2.80-1
ii gnupg 2.2.12-1+deb10u1
ii iproute2 4.20.0-2
ii iptables 1.8.2-4
pn libpam-cgfs <none>
pn lxc-templates <none>
pn lxcfs <none>
ii openssl 1.1.1d-0+deb10u1
ii rsync 3.1.3-6
pn uidmap <none>
Versions of packages lxc suggests:
ii btrfs-progs 4.20.1-2
ii lvm2 2.03.02-3
pn python3-lxc <none>
-- debconf information:
lxc/auto_update_config:
--- End Message ---
--- Begin Message ---
I made a user instruction on how to start an LXC container by a non-root user at
https://wiki.debian.org/LXC/CGroupV2
and I believe that this issue is now resolved. Ryutaroh Matsumoto
--- End Message ---
