Hi All, I am still struggling with the lxc part now. On 25/06/17 19:21, Ross Gammon wrote: > The only thing left to fix is the debci part. The last bit of the update > script output is: > lxc-start: Executing '/sbin/init' with no configuration file may crash > the host > Waiting 30 sec for adt-sid-amd64 to start... > lxc-attach: failed to get the init pid > lxc-attach: failed to get the init pid > lxc-attach: failed to get the init pid I have now deleted the schroot created by the setup script for autopkgtest, as it is clear that it is really an LXC container we are after. In order to get an lxc instead, the setup script needs the "--backend lxc" option added to the "debci setup" command. This is because schroot is the default backend for debci (at least in the version I have on my Jessie laptop). This seemed to create an unstable lxc container. But I still get the same error. Checking out the BTS for lxc, the same "lxc-start: Executing '/sbin/init' with no configuration file may crash the host" error seemed to have been fixed in the version of lxc in jessie-backports, so I installed that. Same problem. The lxc wiki (https://wiki.debian.org/LXC) listed a whole lot of configuration stuff that didn't seem to be setup on my machine after the setup script, so I tried to follow the wiki, changing names where it seemed to be different in the setup script. $ lxc-ls does not reveal any containers. $ lxc-checkconfig says everything is enabled. I can see a directory in "/var/lib/lxc" called "adt-sid-amd64" which is empty apart from a log file with the same errors as above. There are no config file in there. Any clues to how I can fault find this further? Any clues where the container was created? Cheers, Ross
Attachment:
signature.asc
Description: OpenPGP digital signature