On Fri, May 06, 2022 at 07:08:23PM +0100, Julian Gilbey wrote: > On Fri, May 06, 2022 at 02:08:23PM -0300, Antonio Terceiro wrote: > > > [...] > > > 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? > > Yes, they are. It's a standard Debian kernel (currently > linux-image-5.17.0-1-amd64 5.17.3-1). I'm not aware of doing any > customisations that might have caused problems :( > > /etc/lxc/default.conf is unmodified: > > lxc.net.0.type = veth > lxc.net.0.link = lxcbr0 > lxc.net.0.flags = up > > lxc.apparmor.profile = generated > lxc.apparmor.allow_nesting = 1 > > > and when I created a trial container, I get > /var/lib/lxc/debian-unstable-trial/config: > > # Template used to create this container: /usr/share/lxc/templates/lxc-debian > # Parameters passed to the template: -r unstable > # For additional config options, please look at lxc.container.conf(5) > > # Uncomment the following line to support nesting containers: > #lxc.include = /usr/share/lxc/config/nesting.conf > # (Be aware this has security implications) > > lxc.net.0.type = veth > lxc.net.0.hwaddr = 00:16:3e:78:11:12 > lxc.net.0.link = lxcbr0 > lxc.net.0.flags = up > lxc.apparmor.profile = generated > lxc.apparmor.allow_nesting = 1 > lxc.rootfs.path = dir:/var/lib/lxc/debian-unstable-trial/rootfs > > # Common configuration > lxc.include = /usr/share/lxc/config/debian.common.conf > > # Container specific configuration > lxc.tty.max = 4 > lxc.uts.name = debian-unstable-trial > lxc.arch = amd64 > lxc.pty.max = 1024 > > > I've no idea if that is of any help.
I could not find anything wrong in those. I'm sorry but I don't know what's wrong with your system. can you debug to check what is the exact point where it fails to start a container?
signature.asc
Description: PGP signature