Hi,
On Wed, Sep 16, 2020 at 11:14:58PM +0200, Pierre-Elliott Bécue wrote:
> Le mercredi 16 septembre 2020 à 22:08:24+0200, Pierre-Elliott Bécue a écrit :
> > Le vendredi 11 septembre 2020 à 11:12:25+0200, Iñaki Malerba a écrit :
> > > Hi Pebs,
> > >
> > > Thanks for checking this.
> > >
> > >
Le mercredi 16 septembre 2020 à 22:08:24+0200, Pierre-Elliott Bécue a écrit :
> Le vendredi 11 septembre 2020 à 11:12:25+0200, Iñaki Malerba a écrit :
> > Hi Pebs,
> >
> > Thanks for checking this.
> >
> > On Sat, 5 Sep 2020 23:23:30 +0200 Pierre-Elliott =?utf-8?B?QsOpY3Vl?=
> > wrote:>
> > >
Le vendredi 11 septembre 2020 à 11:12:25+0200, Iñaki Malerba a écrit :
> Hi Pebs,
>
> Thanks for checking this.
>
> On Sat, 5 Sep 2020 23:23:30 +0200 Pierre-Elliott =?utf-8?B?QsOpY3Vl?=
> wrote:>
> > LXC's devs told me that 4.0.4 should solve it. I'm uploading this
> > release now. Please don't
Hi Pebs,
Thanks for checking this.
On Sat, 5 Sep 2020 23:23:30 +0200 Pierre-Elliott =?utf-8?B?QsOpY3Vl?=
wrote:>
> LXC's devs told me that 4.0.4 should solve it. I'm uploading this
> release now. Please don't hesitate to tell me if it helps.
Run a pipeline removing the pinning of lxc, and the
Le mercredi 03 juin 2020 à 10:57:13+0200, Inaki Malerba a écrit :
> El 2/6/20 a las 20:07, Pierre-Elliott Bécue escribió:
> > Could you remove the --quiet bit to see if lxc-stop gives us a bit more
> > intel?
> >
> > If possible, have your testbed call lxc-stop --kill --logpriority trace
> >
PS, just to be sure: You do have mounted cgroupv2 on the Docker
host and in the Docker container?
I am using LXC 4.0.2 on about 25 systems without problems. None of these
hosts does nested virtualization, though.
Nested virtualization and cgroups vs cgroups2 is a *highly* complex issue.
Can you reproduce this problem outside of your Docker setup? I wouldn't
like to see LXC dropped for
El 2/6/20 a las 20:07, Pierre-Elliott Bécue escribió:
> Could you remove the --quiet bit to see if lxc-stop gives us a bit more
> intel?
>
> If possible, have your testbed call lxc-stop --kill --logpriority trace
> --logfile /dev/stdout --name ${NAME}, so we can have the most expressive
> output.
Le mardi 26 mai 2020 à 12:55:10+0200, Inaki Malerba a écrit :
> 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
El 26/5/20 a las 23:35, Antonio Terceiro escribió:
> is there an easy/documented way of reproducing the salsa ci environment
> (i.e. lxc working under docker) locally?
Attached is a Dockerfile. It should be sufficient to reproduce the problem.
Changing the FROM statement from debian:unstable to
Control: severity -1 serious
On Tue, May 26, 2020 at 06:35:50PM -0300, Antonio Terceiro wrote:
> 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
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
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
13 matches
Mail list logo
