Package: lxc Version: 1:2.0.7-2 Severity: normal Dear Maintainer,
/usr/sbin/init.lxc.static is not a statically linked executable. So, depending on the the contents of the rootfs of the container being used, it may fail to run. For example, consider a 'wheezy' container running on stretch: # lxc-create -t debian -n wheezy -- -r wheezy [output omitted] # lxc-execute -n wheezy true /init.lxc.static: error while loading shared libraries: libcap.so.2: cannot open shared object file: No such file or directory This seems to be an upstream issue that was fixed in https://github.com/lxc/lxc/commit/d04813f9b5d287dd49520f5afa8a9f6ce6378b09 - could you please backport this patch? -- System Information: Debian Release: 9.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-3-amd64 (SMP w/8 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) Versions of packages lxc depends on: ii init-system-helpers 1.48 ii libapparmor1 2.11.0-3 ii libc6 2.24-11+deb9u1 ii libcap2 1:2.25-1 ii libgnutls30 3.5.8-5+deb9u2 ii liblxc1 1:2.0.7-2 ii libseccomp2 2.3.1-2.1 ii libselinux1 2.6-3+b1 ii lsb-base 9.20161125 ii python3 3.5.3-1 ii python3-lxc 1:2.0.7-2 Versions of packages lxc recommends: ii bridge-utils 1.5-13 ii debootstrap 1.0.89 ii dirmngr 2.1.18-6 ii dnsmasq-base 2.76-5+b1 ii gnupg 2.1.18-6 ii iptables 1.6.0+snapshot20161117-6 ii libpam-cgfs 2.0.7-1 ii lxcfs 2.0.7-1 ii openssl 1.1.0f-3 ii rsync 3.1.2-1 ii uidmap 1:4.4-4.1 Versions of packages lxc suggests: pn apparmor <none> pn btrfs-tools <none> ii lvm2 2.02.168-2 -- no debconf information
