This situation causes a problem whenever trying to remove an old Python
version within an LXC container/guest.
E.g. after a dist-upgrade from Debian 10 to 11, running apt autoremove:
Removing python3.7 (3.7.3-2+deb10u3) ...
Removing libpython3.7-stdlib:amd64 (3.7.3-2+deb10u3) ...
Removing python3
Hello Colin Watson,
the following should work (either directory install or on LVM,
choosing buster or testing):
RELEASE="buster"
#RELEASE="testing"
#LVM="--bdev lvm --lvname lxc-debian05 --vgname debvg --fssize 30G"
sudo lxc-create -n debian05 $LVM -t debian -- -r $RELEASE
--enable-non-free --aut
On Sun, Jun 14, 2020 at 01:55:45PM +0200, Florian La Roche wrote:
> Installing Debian stable within lxc gives warnings/errors for
> binfmt-support. Expected and nothing unusual. Maybe you can detect lxc
> and just not enable any access to /proc/sys/fs/binfmt_misc?
> Thos only occurs with Debian sta
Package: binfmt-support
Version: 2.2.1-1
Severity: normal
Dear Maintainer,
Installing Debian stable within lxc gives warnings/errors for
binfmt-support. Expected and nothing unusual. Maybe you can detect lxc
and just not enable any access to /proc/sys/fs/binfmt_misc?
Thos only occurs with Debian
4 matches
Mail list logo
