On Fri, May 06, 2022 at 04:13:28PM +0100, Julian Gilbey wrote: > [excluding 1010437@bugs.d.o from reply list, as that's to do with > eatmydata] > > On Fri, May 06, 2022 at 08:53:35AM -0300, Antonio Terceiro wrote: > > > [...] > > > And I'm on 1:4.0.11-1. So perhaps there was a regression in this > > > regard? > > > > No. I use this version and lxc just works for me. In fact everyone else > > who is on testing/unstable is also using it. lxc also just works on a > > clean VM. There is something wrong with your system that is causing > > this, but it's in no way a general problem. > > Dear Antonio, > > It seems that you are right: I tried booting into Debian Live, > upgrading to testing and running lxc; it ran without a problem. > > So now I'm in a quandry: despite installing lxc from scratch, and just > redoing so (purging the packages and removing all of the cached files, > /etc/lxc, /var/lib/lxc* and so on before reinstalling), I am still > experiencing the same problem. I am running what I believe to be a > standard system - I first installed it in September 2020 or > thereabouts and have kept it up-to-date with testing ever since. I > have no idea what might be causing this strange behaviour, and > therefore I have got no clue how to fix it. I also don't know whether > what is wrong with my setup might affect other people as well. > > If you have any suggestions of things I could look at on my system > (configuration files, other packages, ...) I'm all ears!
Are all packages recommended by lxc installed?
signature.asc
Description: PGP signature
