Your message dated Fri, 3 Feb 2023 09:55:46 +0000
with message-id <Y9zaIhoKP3NIS+y5@???>
and subject line Re: bug#445: lxc-start and lxc-execute cause segfault started by non-root and completely unusable
has caused the Devuan bug report #445,
regarding lxc-start and lxc-execute cause segfault started by non-root without libpam-cgfs
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 owner@???
immediately.)


--
445: https://bugs.devuan.org/cgi/bugreport.cgi?bug=445
Devuan Bug Tracking System
Contact owner@??? with problems
Package: lxc
Version: 1:3.1.0+really3.0.3-8
Severity: grave
Justification: renders package unusable

Dear Maintainer,

On a Devuan Beowulf (running on qemu-kvm), as root I can use the lxc package
with no problem. Thank you. As root, "lxc-start -F -n beowulf" works fine
in the below qemu-kvm image.

But when lxc-execute or lxc-start is run by a non-root user, they always give
segmentation fault and are completely unsable (screenshot attached).
One of claimed advantages of lxc is to allow non-root users to use containers,
but Devuan users cannot enjoy it...

The container's rootfs tree was prepared by

mmdebstrap --mode=unshare --components="main contrib non-free" --variant=standard beowulf $HOME/.local/share/lxc/beowulf/rootfs http://deb.devuan.org/merged

The screenshot and the qemu-kvm disk image (qcow file) are placed at

https://drive.google.com/drive/u/0/folders/1wDNYOYjt7XhMAl-ky7EsviGI-bowalc7

Its root password is "root" and the password of user "ryutaroh" is "ryutaroh".
/etc/default/keyboard is set to the Japanese layout, and may need editting.
So you should be able to reproduce this bug in your computer at hand.

Best regards, Ryutaroh Matsumoto

-- System Information:
Distributor ID:    Debian
Description:    Devuan GNU/Linux 3 (beowulf)
Release:    3
Codename:    beowulf
Architecture: x86_64

Kernel: Linux 4.19.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages lxc depends on:
ii  debconf [debconf-2.0]  1.5.71
ii  libc6                  2.28-10
ii  libcap2                1:2.25-2
ii  libgnutls30            3.6.7-4+deb10u3
ii  liblxc1                1:3.1.0+really3.0.3-8
ii  libseccomp2            2.3.3-4
ii  libselinux1            2.8-1+b1
ii  lsb-base               10.2019051400

Versions of packages lxc recommends:
ii  apparmor                     2.13.2-10
ii  bridge-utils                 1.6-2
pn  debootstrap                  <none>
pn  dirmngr                      <none>
ii  dnsmasq-base [dnsmasq-base]  2.80-1
pn  gnupg                        <none>
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+deb10u3
pn  rsync                        <none>
ii  uidmap                       1:4.5-1.1

Versions of packages lxc suggests:
ii  btrfs-progs  4.20.1-2
pn  lvm2         <none>
pn  python3-lxc  <none>

-- debconf information:
lxc/auto_update_config:

On Sun, May 10, 2020 at 09:18:58AM +0100, Mark Hindley wrote:
> Control: tags -1 debian
>
> On Sun, May 10, 2020 at 09:47:04AM +0900, Ryutaroh Matsumoto wrote:
> > > Does your unprivileged user have write access to cgroups? That appears to be a
> > > common cause of this from a quick internet search.
> >
> > The cause was that I did not install libpam-cgfs package.
> > You are welcome to close this

Closing.

Mark