Greetings, Ross Gammon! > Hi,
> I am new to the list, as am having problems that are probably caused by > some old lxc containers that I can't seem to get rid of. > I would like to use the pkg-ruby/meta scripts to run the autopkgtests in > my Debian packages locally, on my Ubuntu bionic machine. But I seem to > have got myself in a mess with previous attempts to set up debci. > The setup script is here: > https://salsa.debian.org/ruby-team/meta/blob/master/setup > It sets up some lxc parameters, and then runs: $ sudo auto-apt-proxy > debci setup > I get: > Starting testbed setup: Thu Nov 15 17:10:18 CET 2018 > Error creating container autopkgtest-sid-amd64 > Failed to load config for adt-sid-amd64 > Failed to load config for autopkgtest-lxc-jnxotl > Failed to load config for autopkgtest-lxc-pclpbt > Failed to load config for autopkgtest-lxc-qhzbek > Failed to load config for autopkgtest-sid > Failed to load config for adt-sid-amd64 > Failed to load config for autopkgtest-lxc-jnxotl > Failed to load config for autopkgtest-lxc-pclpbt > Failed to load config for autopkgtest-lxc-qhzbek > Failed to load config for autopkgtest-sid > The problem has been there for a while, but I thought I would try and > track down the issue today. Today, I followed the documentation > https://linuxcontainers.org/lxc/getting-started/ and everything is > working fine for general lxc usage. > But none of the lxc commands can find the above containers or > delete/destroy them though. I can see the named containers with: > $ sudo ls /var/lib/lxc/ > adt-sid-amd64 autopkgtest-lxc-pclpbt autopkgtest-sid > autopkgtest-lxc-jnxotl autopkgtest-lxc-qhzbek > How can I delete them? Alternatively, does anyone know another way to > create a suitable container called autopkgtest-sid-amd64 in Ubuntu? First, make distinction between LXC and LXD. LXC provide containers per se, and a minimal interface to manage them in the form of separate "lxc-something" tools. LXD provide a much better managements and clusterization interface in the form of a single "lxc" tool. Now, I think your issue is that your containers are using old config syntax. You can either rm -rf them and try again, or manually edit each config to match relevant configuration options to new keys. -- With best regards, Andrey Repin Thursday, November 15, 2018 23:43:12 Sorry for my terrible english... _______________________________________________ lxc-users mailing list [email protected] http://lists.linuxcontainers.org/listinfo/lxc-users
