[pkg-lxc-devel] Bug#961584: lxc-stop fails with exit code 1

Antonio Terceiro terceiro at debian.org
Tue May 26 22:35:46 BST 2020


On Tue, May 26, 2020 at 12:55:10PM +0200, Inaki Malerba wrote:
> Source: lxc
> Version: 1:4.0.2-1
> Severity: important
> 
> Dear Maintainer,
> 
> Since version 1:4.0.2-1, we've found a change on the behavior of
> lxc-stop when running on the Salsa-CI pipeline.
> 
> debci calls `lxc-stop --quiet --kill --name $NAME` and it's returning
> exit code 1.
> 
> This can be reproduced on salsa-ci pipeline, which calls `debci localtest`.
> 
> https://salsa.debian.org/salsa-ci-team/pipeline/-/jobs/765946
> 
> <VirtSubproc>: failure: ['sudo', 'timeout', '600', 'lxc-stop',
> '--quiet', '--kill', '--name', 'ci-147-3f089355'] failed (exit status 1,
> stderr '')

I have been using this version of lxc locally for autopkgtest for a
while without any issues, so this issue is probably specific to running
lxc under docker.

is there an easy/documented way of reproducing the salsa ci environment
(i.e. lxc working under docker) locally? I downloaded
registry.salsa.debian.org/salsa-ci-team/pipeline/autopkgtest, started a
container with --privileged, and tried following the steps in the
salsa-ci-yml, but I am probably missing something because the containers
won't start apparently due to apparmor.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-lxc-devel/attachments/20200526/81ea158b/attachment.sig>


More information about the Pkg-lxc-devel mailing list