Package: lxc Version: 1:2.0.9-6.1 Severity: normal Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate *** After upgrade kernel to linux-image-4.18.0-1-amd64, I can not start unprivileged LXC containers, Maybe related to this one "https://lists.linuxfoundation.org/pipermail/containers/2018-June/039174.html", and "https://github.com/lxc/lxc/pull/2438". Please help and thank you. * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-1-amd64 (SMP w/2 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: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lxc depends on: ii libapparmor1 2.13-8 ii libc6 2.27-6 ii libcap2 1:2.25-1.2 ii libgnutls30 3.5.19-1 ii liblxc1 1:2.0.9-6.1 ii libseccomp2 2.3.3-3 ii libselinux1 2.8-1+b1 ii lsb-base 9.20170808 ii python3 3.6.6-1 ii python3-lxc 1:2.0.9-6.1 Versions of packages lxc recommends: ii bridge-utils 1.5-16 pn debootstrap <none> ii dirmngr 2.2.10-1 pn dnsmasq-base <none> ii gnupg 2.2.10-1 ii iptables 1.6.2-1.1 pn libpam-cgfs <none> pn lxcfs <none> ii openssl 1.1.1~~pre9-1 ii rsync 3.1.2-2.2 pn uidmap <none> Versions of packages lxc suggests: ii apparmor 2.13-8 ii btrfs-progs 4.17-1 pn lvm2 <none> -- no debconf information