Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1101908 > unrolled thread

Bug#1010437: autopkgtest: autopkgtest-build-lxc fails to build working lxc environment

Back to article view | Back to linux.debian.bugs.dist

Contents

  Bug#1010437: autopkgtest: autopkgtest-build-lxc fails to build working lxc environment Julian Gilbey <jdg@debian.org> - 2022-05-01 17:10 +0200
    Bug#1010437: autopkgtest: autopkgtest-build-lxc fails to build working lxc environment Julian Gilbey <jdg@debian.org> - 2022-05-02 09:30 +0200
      Bug#1010437: autopkgtest: autopkgtest-build-lxc fails to build working lxc environment Julian Gilbey <jdg@debian.org> - 2022-05-03 18:30 +0200
        Bug#1010437: autopkgtest: autopkgtest-build-lxc fails to build working lxc environment Paul Gevers <elbrus@debian.org> - 2022-05-03 18:40 +0200
          Bug#1010437: autopkgtest: autopkgtest-build-lxc fails to build working lxc environment Julian Gilbey <jdg@debian.org> - 2022-05-06 09:30 +0200
            Bug#1010437: autopkgtest: autopkgtest-build-lxc fails to build working lxc environment Antonio Terceiro <terceiro@debian.org> - 2022-05-06 14:00 +0200
              Bug#1010469: Bug#1010437: autopkgtest: autopkgtest-build-lxc fails to build working lxc environment Julian Gilbey <jdg@debian.org> - 2022-05-06 17:20 +0200
                Bug#1010469: Bug#1010437: autopkgtest: autopkgtest-build-lxc fails to build working lxc environment Antonio Terceiro <terceiro@debian.org> - 2022-05-06 19:20 +0200
                  Bug#1010469: Bug#1010437: autopkgtest: autopkgtest-build-lxc fails to build working lxc environment Julian Gilbey <jdg@debian.org> - 2022-05-06 20:20 +0200
                    Bug#1010469: Bug#1010437: autopkgtest: autopkgtest-build-lxc fails to build working lxc environment Antonio Terceiro <terceiro@debian.org> - 2022-05-11 20:10 +0200
                      Bug#1010469: Bug#1010437: autopkgtest: autopkgtest-build-lxc fails to build working lxc environment Julian Gilbey <jdg@debian.org> - 2022-05-11 22:50 +0200
                      Bug#1010469: Bug#1010437: autopkgtest: autopkgtest-build-lxc fails to build working lxc environment Julian Gilbey <jdg@debian.org> - 2022-05-31 13:20 +0200
                        Bug#1010469: Bug#1010437: autopkgtest: autopkgtest-build-lxc fails to build working lxc environment Julian Gilbey <jdg@debian.org> - 2022-06-08 11:00 +0200

#1101908 — Bug#1010437: autopkgtest: autopkgtest-build-lxc fails to build working lxc environment

Package: autopkgtest
Version: 5.21
Severity: normal

(I realise that posting this on debian-devel [1] was probably not the
most appropriate place, as it's actually a bug report.)

I am not sure whether this is a bug in autopkgtest-build-lxc, a bug in
lxc itself or a user error.  Please feel free to redirect as
appropriate!

This is what I did:

Step 1: I installed the lxc and autopkgtest packages
That went smoothly.  (lxc version 1:4.0.11-1, autopkgtest version
5.21; autopkgtest was already installed, and I installed lxc from 

Step 2: I ran the command "autopkgtest-build-lxc debian sid"
as root.  I got various warning messages to begin with:

>>>>>
lxc-create: autopkgtest-sid: storage/btrfs.c: btrfs_create: 938 Inappropriate ioctl for device - Failed to create btrfs subvolume "/var/lib/lxc/autopkgtest-sid/rootfs"
lxc-create: autopkgtest-sid: storage/zfs.c: zfs_create: 735 Failed to create zfs dataset "zfs:lxc/autopkgtest-sid": lxc-create: autopkgtest-sid: utils.c: run_command_internal: 1588
lxc-create: autopkgtest-sid: storage/lvm.c: do_lvm_create: 165 Failed to create logical volume "autopkgtest-sid":   Volume group "lxc" not found
  Cannot process volume group lxc
lxc-create: autopkgtest-sid: storage/lvm.c: lvm_create: 623 Error creating new logical volume "lvm:/dev/lxc/autopkgtest-sid" of size "1073741824 bytes"
<<<<<

after which things ran smoothly for a bit:

>>>>>
debootstrap is /usr/sbin/debootstrap
Checking cache download in /var/cache/lxc/debian/rootfs-sid-amd64 ... 
Downloading debian minimal ...
I: Target architecture can be executed
I: Retrieving InRelease 
[... downloading and installing base system ...]
I: Base system installed successfully.
Download complete.
<<<<<

but then there were lots of warning messages about libeatmydata.so
interspersed with information messages; I assume that these are mostly
harmless:

>>>>>
Copying rootfs to /var/lib/lxc/autopkgtest-sid/rootfs...ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
Generating locales (this might take a while)...
ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
  en_GB.UTF-8ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
[... lots more similar warnings and messages ...]
ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
<<<<<

But then I received several fatal error messages:

>>>>>
lxc-start: autopkgtest-sid: lxccontainer.c: wait_on_daemonized_start: 867 Received container state "ABORTING" instead of "RUNNING"
lxc-start: autopkgtest-sid: tools/lxc_start.c: main: 306 The container failed to start
lxc-start: autopkgtest-sid: tools/lxc_start.c: main: 309 To get more details, run the container in foreground mode
lxc-start: autopkgtest-sid: tools/lxc_start.c: main: 311 Additional information can be obtained by setting the --logfile and --logpriority options
<<<<<

Since autopkgtest-build-lxc doesn't allow a --logfile option, I
attempted to start the container manually, using the command
  lxc-start -n autopkgtest-sid --logfile /tmp/lxc.log --logpriority INFO
and got the following warnings and errors in the log file (I've
excluded the INFO entries):

>>>>>
lxc-start autopkgtest-sid 20220501145802.680 NOTICE   conf - conf.c:lxc_setup:4450 - The container "autopkgtest-sid" is set up
lxc-start autopkgtest-sid 20220501145802.681 WARN     cgfsng - cgroups/cgfsng.c:get_hierarchy:142 - There is no useable devices controller
lxc-start autopkgtest-sid 20220501145802.681 ERROR    cgfsng - cgroups/cgfsng.c:cg_legacy_set_data:2675 - No such file or directory - Failed to setup limits for the "devices" controller. The controller seems to be unused by "cgfsng" cgroup driver or not enabled on the cgroup hierarchy
lxc-start autopkgtest-sid 20220501145802.681 ERROR    cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits_legacy:2742 - No such file or directory - Failed to set "devices.deny" to "a"
lxc-start autopkgtest-sid 20220501145802.681 ERROR    start - start.c:lxc_spawn:1890 - Failed to setup legacy device cgroup controller limits
lxc-start autopkgtest-sid 20220501145802.681 ERROR    lxccontainer - lxccontainer.c:wait_on_daemonized_start:867 - Received container state "ABORTING" instead of "RUNNING"
lxc-start autopkgtest-sid 20220501145802.681 ERROR    lxc_start - tools/lxc_start.c:main:306 - The container failed to start
lxc-start autopkgtest-sid 20220501145802.681 ERROR    lxc_start - tools/lxc_start.c:main:309 - To get more details, run the container in foreground mode
lxc-start autopkgtest-sid 20220501145802.681 ERROR    lxc_start - tools/lxc_start.c:main:311 - Additional information can be obtained by setting the --logfile and --logpriority options
lxc-start autopkgtest-sid 20220501145802.682 ERROR    start - start.c:__lxc_start:2068 - Failed to spawn container "autopkgtest-sid"
lxc-start autopkgtest-sid 20220501145802.682 WARN     start - start.c:lxc_abort:1038 - No such process - Failed to send SIGKILL via pidfd 20 for process 389747
<<<<<

I found something like this reported at this GitHub issue against lxc:
https://github.com/lxc/lxc/issues/2268
so I followed the advice there and ran the commands:

mount -o remount,rw /sys/fs/cgroup
mkdir /sys/fs/cgroup/devices
mount -t cgroup devices -o devices /sys/fs/cgroup/devices
mount -o remount,ro /sys/fs/cgroup

But that seems to be really bad, as now systemd-logind.service seems
to have broken and cannot be restarted, so I don't recommend doing
that!

I've restarted my system and started again.  The above solution is
very bad at least partly because /sys/fs/cgroup is type cgroup2.  But
I still can't start the LXC container, which makes running autopkgtest
impossible.

I did read the Debian Wiki pages on LXC and the
/usr/share/doc/lxc/README.Debian.gz file, but to no avail.  (I do have
apparmor installed.)

Any help much appreciated!

Best wishes,

   Julian


[1] https://lists.debian.org/debian-devel/2022/04/msg00372.html


-- System Information:
Debian Release: bookworm/sid
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.17.0-1-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages autopkgtest depends on:
ii  apt-utils       2.4.5
ii  libdpkg-perl    1.21.7
ii  procps          2:3.3.17-7+b1
ii  python3         3.10.4-1
ii  python3-debian  0.1.43

Versions of packages autopkgtest recommends:
ii  autodep8  0.26

Versions of packages autopkgtest suggests:
pn  fakemachine       <none>
pn  lxc               <none>
pn  lxd               <none>
pn  ovmf              <none>
pn  ovmf-ia32         <none>
pn  qemu-efi-aarch64  <none>
pn  qemu-efi-arm      <none>
pn  qemu-system       <none>
pn  qemu-utils        <none>
ii  schroot           1.6.10-12
pn  vmdb2             <none>

-- no debconf information

[toc] | [next] | [standalone]

#1101981

clone 1010437 -1
reassign -1 lxc 1:4.0.11-1
retitle -1 lxc: as root, lxc-start fails to start with cgroups/cgfsng error setting up limits for devices
retitle 1010437 autopkgtest-build-lxc: eatmydata gives lots of LD_PRELOAD warnings
thanks

I have now run the autopkgtest-build-lxc script "by hand" to see where
the issues are arising in the issue below, and I think there are two
separate things going on, hence splitting this bug report into two.
A few comments interspersed below.

On Sun, May 01, 2022 at 04:03:09PM +0100, Julian Gilbey wrote:
> Package: autopkgtest
> Version: 5.21
> Severity: normal
> 
> (I realise that posting this on debian-devel [1] was probably not the
> most appropriate place, as it's actually a bug report.)
> 
> I am not sure whether this is a bug in autopkgtest-build-lxc, a bug in
> lxc itself or a user error.  Please feel free to redirect as
> appropriate!
> 
> This is what I did:
> 
> Step 1: I installed the lxc and autopkgtest packages
> That went smoothly.  (lxc version 1:4.0.11-1, autopkgtest version
> 5.21; autopkgtest was already installed, and I installed lxc from 
> 
> Step 2: I ran the command "autopkgtest-build-lxc debian sid"
> as root.  I got various warning messages to begin with:
> 
> >>>>>
> lxc-create: autopkgtest-sid: storage/btrfs.c: btrfs_create: 938 Inappropriate ioctl for device - Failed to create btrfs subvolume "/var/lib/lxc/autopkgtest-sid/rootfs"
> lxc-create: autopkgtest-sid: storage/zfs.c: zfs_create: 735 Failed to create zfs dataset "zfs:lxc/autopkgtest-sid": lxc-create: autopkgtest-sid: utils.c: run_command_internal: 1588
> lxc-create: autopkgtest-sid: storage/lvm.c: do_lvm_create: 165 Failed to create logical volume "autopkgtest-sid":   Volume group "lxc" not found
>   Cannot process volume group lxc
> lxc-create: autopkgtest-sid: storage/lvm.c: lvm_create: 623 Error creating new logical volume "lvm:/dev/lxc/autopkgtest-sid" of size "1073741824 bytes"
> <<<<<
> 
> after which things ran smoothly for a bit:
> 
> >>>>>
> debootstrap is /usr/sbin/debootstrap
> Checking cache download in /var/cache/lxc/debian/rootfs-sid-amd64 ... 
> Downloading debian minimal ...
> I: Target architecture can be executed
> I: Retrieving InRelease 
> [... downloading and installing base system ...]
> I: Base system installed successfully.
> Download complete.
> <<<<<
> 
> but then there were lots of warning messages about libeatmydata.so
> interspersed with information messages; I assume that these are mostly
> harmless:
> 
> >>>>>
> Copying rootfs to /var/lib/lxc/autopkgtest-sid/rootfs...ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
> ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
> Generating locales (this might take a while)...
> ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
>   en_GB.UTF-8ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
> [... lots more similar warnings and messages ...]
> ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
> <<<<<

This looks to be similar to
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963508 so I wonder
whether the apparmor settings for lxc mean that LD_PRELOAD cannot be
used with lxc, and LD_PRELOAD is needed by eatmydata.  This is a minor
issue with autopkgtest-build-lxc; maybe it should just not try using
eatmydata, or maybe there is some way to change the lxc apparmor
settings (if indeed that is the thing preventing the use of
LD_PRELOAD) to allow eatmydata?  I don't know anything about apparmor,
so I am just speculating here.


> But then I received several fatal error messages:
> 
> >>>>>
> lxc-start: autopkgtest-sid: lxccontainer.c: wait_on_daemonized_start: 867 Received container state "ABORTING" instead of "RUNNING"
> lxc-start: autopkgtest-sid: tools/lxc_start.c: main: 306 The container failed to start
> lxc-start: autopkgtest-sid: tools/lxc_start.c: main: 309 To get more details, run the container in foreground mode
> lxc-start: autopkgtest-sid: tools/lxc_start.c: main: 311 Additional information can be obtained by setting the --logfile and --logpriority options
> <<<<<
> 
> Since autopkgtest-build-lxc doesn't allow a --logfile option, I
> attempted to start the container manually, using the command
>   lxc-start -n autopkgtest-sid --logfile /tmp/lxc.log --logpriority INFO
> and got the following warnings and errors in the log file (I've
> excluded the INFO entries):
> 
> >>>>>
> lxc-start autopkgtest-sid 20220501145802.680 NOTICE   conf - conf.c:lxc_setup:4450 - The container "autopkgtest-sid" is set up
> lxc-start autopkgtest-sid 20220501145802.681 WARN     cgfsng - cgroups/cgfsng.c:get_hierarchy:142 - There is no useable devices controller
> lxc-start autopkgtest-sid 20220501145802.681 ERROR    cgfsng - cgroups/cgfsng.c:cg_legacy_set_data:2675 - No such file or directory - Failed to setup limits for the "devices" controller. The controller seems to be unused by "cgfsng" cgroup driver or not enabled on the cgroup hierarchy
> lxc-start autopkgtest-sid 20220501145802.681 ERROR    cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits_legacy:2742 - No such file or directory - Failed to set "devices.deny" to "a"
> lxc-start autopkgtest-sid 20220501145802.681 ERROR    start - start.c:lxc_spawn:1890 - Failed to setup legacy device cgroup controller limits
> lxc-start autopkgtest-sid 20220501145802.681 ERROR    lxccontainer - lxccontainer.c:wait_on_daemonized_start:867 - Received container state "ABORTING" instead of "RUNNING"
> lxc-start autopkgtest-sid 20220501145802.681 ERROR    lxc_start - tools/lxc_start.c:main:306 - The container failed to start
> lxc-start autopkgtest-sid 20220501145802.681 ERROR    lxc_start - tools/lxc_start.c:main:309 - To get more details, run the container in foreground mode
> lxc-start autopkgtest-sid 20220501145802.681 ERROR    lxc_start - tools/lxc_start.c:main:311 - Additional information can be obtained by setting the --logfile and --logpriority options
> lxc-start autopkgtest-sid 20220501145802.682 ERROR    start - start.c:__lxc_start:2068 - Failed to spawn container "autopkgtest-sid"
> lxc-start autopkgtest-sid 20220501145802.682 WARN     start - start.c:lxc_abort:1038 - No such process - Failed to send SIGKILL via pidfd 20 for process 389747
> <<<<<
> [...]

This also happens when I create the lxc container manually (as root),
using the recipe in autopkgtest-build-lxc:
  lxc-create -B best --name=autopkgtest-unstable -t debian -- -r unstable
the resulting container fails to start in the same way as just
described (when lxc-start is run as root).

This is the bug report against lxc.

Best wishes,

   Julian

[toc] | [prev] | [next] | [standalone]

#1102135

An update...

On Mon, May 02, 2022 at 08:21:13AM +0100, Julian Gilbey wrote:
> [...]
> > Since autopkgtest-build-lxc doesn't allow a --logfile option, I
> > attempted to start the container manually, using the command
> >   lxc-start -n autopkgtest-sid --logfile /tmp/lxc.log --logpriority INFO
> > and got the following warnings and errors in the log file (I've
> > excluded the INFO entries):
> > 
> > >>>>>
> [...]
> > lxc-start autopkgtest-sid 20220501145802.681 ERROR    cgfsng - cgroups/cgfsng.c:cg_legacy_set_data:2675 - No such file or directory - Failed to setup limits for the "devices" controller. The controller seems to be unused by "cgfsng" cgroup driver or not enabled on the cgroup hierarchy
> > lxc-start autopkgtest-sid 20220501145802.681 ERROR    cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits_legacy:2742 - No such file or directory - Failed to set "devices.deny" to "a"
> [...]

I've now done more searching, and the conclusion I've come to is that
this is that this is the same issue discussed in
https://wiki.debian.org/LXC/CGroupV2#LXC_containers_started_by_root
(and in various other bug reports); by adding the two lines

lxc.cgroup.devices.allow =
lxc.cgroup.devices.deny =

to the file /var/lib/lxc/autopkgtest-unstable/config, I was able to
start the container.  But I'm running lxc version 1:4.0.11-1 and that
wiki page says this change is unnecessary from version 4.0.2-1~1
onwards, which does not seem to be the case.

lxc: I don't know whether the wiki is wrong or some change made in
4.0.2-1 has been reverted more recently.  Either way, it would be
great to resolve this discrepancy.

autopkgtest-build-lxc: perhaps it would be good to add these lines at
the end of the config file when the container is built, especially if
the lxc folks can't fix this.

Best wishes,

   Julian

[toc] | [prev] | [next] | [standalone]

#1102137

[Multipart message — attachments visible in raw view] — view raw

Hi Julian,

Sorry for the silence, you're doing great work.

On 03-05-2022 18:19, Julian Gilbey wrote:
> I've now done more searching, and the conclusion I've come to is that
> this is that this is the same issue discussed in
> https://wiki.debian.org/LXC/CGroupV2#LXC_containers_started_by_root
> (and in various other bug reports); by adding the two lines

I wonder if you refer to
https://bugs.debian.org/902394
https://bugs.debian.org/904732

Our infrastructure (where we don't experiences issues and are using the 
autopkgtest/debci/autodep8 packages from unstable on an otherwise stable 
system) runs lxc version 1:4.0.6-2. So that maybe limiting the changes 
further.

Paul

[toc] | [prev] | [next] | [standalone]

#1102410

Hi Paul and lxc maintainers,

lxc maintainers: sorry, I intended to copy in #1010469 in my previous
message but didn't do so; a possible cause of this bug is discussed
below

On Tue, May 03, 2022 at 06:36:36PM +0200, Paul Gevers wrote:
> Hi Julian,
> 
> Sorry for the silence, you're doing great work.

Yes, I was determined to get it to work!

> On 03-05-2022 18:19, Julian Gilbey wrote:
> > I've now done more searching, and the conclusion I've come to is that
> > this is that this is the same issue discussed in
> > https://wiki.debian.org/LXC/CGroupV2#LXC_containers_started_by_root
> > (and in various other bug reports); by adding the two lines
> > 
> > lxc.cgroup.devices.allow =
> > lxc.cgroup.devices.deny =
> > 
> > to the file /var/lib/lxc/autopkgtest-unstable/config, I was able to
> > start the container.  But I'm running lxc version 1:4.0.11-1 and that
> > wiki page says this change is unnecessary from version 4.0.2-1~1
> > onwards, which does not seem to be the case.
> > 
> > lxc: I don't know whether the wiki is wrong or some change made in
> > 4.0.2-1 has been reverted more recently.  Either way, it would be
> > great to resolve this discrepancy.
> 
> I wonder if you refer to
> https://bugs.debian.org/902394
> https://bugs.debian.org/904732

I was thinking more of
https://bugs.debian.org/944389

> Our infrastructure (where we don't experiences issues and are using the
> autopkgtest/debci/autodep8 packages from unstable on an otherwise stable
> system) runs lxc version 1:4.0.6-2. So that maybe limiting the changes
> further.

And I'm on 1:4.0.11-1.  So perhaps there was a regression in this
regard?

Best wishes,

   Julian

[toc] | [prev] | [next] | [standalone]

#1102428

[Multipart message — attachments visible in raw view] — view raw

On Fri, May 06, 2022 at 08:15:58AM +0100, Julian Gilbey wrote:
> Hi Paul and lxc maintainers,
> 
> lxc maintainers: sorry, I intended to copy in #1010469 in my previous
> message but didn't do so; a possible cause of this bug is discussed
> below
> 
> On Tue, May 03, 2022 at 06:36:36PM +0200, Paul Gevers wrote:
> > Hi Julian,
> > 
> > Sorry for the silence, you're doing great work.
> 
> Yes, I was determined to get it to work!
> 
> > On 03-05-2022 18:19, Julian Gilbey wrote:
> > > I've now done more searching, and the conclusion I've come to is that
> > > this is that this is the same issue discussed in
> > > https://wiki.debian.org/LXC/CGroupV2#LXC_containers_started_by_root
> > > (and in various other bug reports); by adding the two lines
> > > 
> > > lxc.cgroup.devices.allow =
> > > lxc.cgroup.devices.deny =
> > > 
> > > to the file /var/lib/lxc/autopkgtest-unstable/config, I was able to
> > > start the container.  But I'm running lxc version 1:4.0.11-1 and that
> > > wiki page says this change is unnecessary from version 4.0.2-1~1
> > > onwards, which does not seem to be the case.
> > > 
> > > lxc: I don't know whether the wiki is wrong or some change made in
> > > 4.0.2-1 has been reverted more recently.  Either way, it would be
> > > great to resolve this discrepancy.
> > 
> > I wonder if you refer to
> > https://bugs.debian.org/902394
> > https://bugs.debian.org/904732
> 
> I was thinking more of
> https://bugs.debian.org/944389
> 
> > Our infrastructure (where we don't experiences issues and are using the
> > autopkgtest/debci/autodep8 packages from unstable on an otherwise stable
> > system) runs lxc version 1:4.0.6-2. So that maybe limiting the changes
> > further.
> 
> And I'm on 1:4.0.11-1.  So perhaps there was a regression in this
> regard?

No. I use this version and lxc just works for me. In fact everyone else
who is on testing/unstable is also using it. lxc also just works on a
clean VM. There is something wrong with your system that is causing
this, but it's in no way a general problem.

[toc] | [prev] | [next] | [standalone]

#1102445 — Bug#1010469: Bug#1010437: autopkgtest: autopkgtest-build-lxc fails to build working lxc environment

[excluding 1010437@bugs.d.o from reply list, as that's to do with
eatmydata]

On Fri, May 06, 2022 at 08:53:35AM -0300, Antonio Terceiro wrote:
> > [...]
> > And I'm on 1:4.0.11-1.  So perhaps there was a regression in this
> > regard?
> 
> No. I use this version and lxc just works for me. In fact everyone else
> who is on testing/unstable is also using it. lxc also just works on a
> clean VM. There is something wrong with your system that is causing
> this, but it's in no way a general problem.

Dear Antonio,

It seems that you are right: I tried booting into Debian Live,
upgrading to testing and running lxc; it ran without a problem.

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!

Many thanks,

   Julian

[toc] | [prev] | [next] | [standalone]

#1102452 — Bug#1010469: Bug#1010437: autopkgtest: autopkgtest-build-lxc fails to build working lxc environment

[Multipart message — attachments visible in raw view] — view raw

On Fri, May 06, 2022 at 04:13:28PM +0100, Julian Gilbey wrote:
> [excluding 1010437@bugs.d.o from reply list, as that's to do with
> eatmydata]
> 
> On Fri, May 06, 2022 at 08:53:35AM -0300, Antonio Terceiro wrote:
> > > [...]
> > > And I'm on 1:4.0.11-1.  So perhaps there was a regression in this
> > > regard?
> > 
> > No. I use this version and lxc just works for me. In fact everyone else
> > who is on testing/unstable is also using it. lxc also just works on a
> > clean VM. There is something wrong with your system that is causing
> > this, but it's in no way a general problem.
> 
> Dear Antonio,
> 
> It seems that you are right: I tried booting into Debian Live,
> upgrading to testing and running lxc; it ran without a problem.
> 
> 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?

[toc] | [prev] | [next] | [standalone]

#1102456 — Bug#1010469: Bug#1010437: autopkgtest: autopkgtest-build-lxc fails to build working lxc environment

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.

Thanks!

   Julian

[toc] | [prev] | [next] | [standalone]

#1102828 — Bug#1010469: Bug#1010437: autopkgtest: autopkgtest-build-lxc fails to build working lxc environment

[Multipart message — attachments visible in raw view] — view raw

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?

[toc] | [prev] | [next] | [standalone]

#1102842 — Bug#1010469: Bug#1010437: autopkgtest: autopkgtest-build-lxc fails to build working lxc environment

On Wed, May 11, 2022 at 03:03:54PM -0300, Antonio Terceiro wrote:
> On Fri, May 06, 2022 at 07:08:23PM +0100, Julian Gilbey wrote:
> [...]
> > 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?

Thanks Antonio!

Here's a log file with logpriority at DEBUG; I've no idea if this will
help.  I'm so stumped.  I wondered if it was perhaps some extra kernel
modules (using dkms) causing the problem, so I've purged those and
rebooted, but it didn't help.

Something seems to be confused with the cgroups.  Here's the result of
mount | grep cgroup:
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime)
none on /sys/fs/cgroup/net_cls type cgroup (rw,relatime,net_cls)

And ls /sys/fs/cgroup gives:

cgroup.controllers	dev-hugepages.mount  misc.capacity
cgroup.max.depth	dev-mqueue.mount     net_cls
cgroup.max.descendants	init.scope	     proc-fs-nfsd.mount
cgroup.procs		io.cost.model	     proc-sys-fs-binfmt_misc.mount
cgroup.stat		io.cost.qos	     sys-fs-fuse-connections.mount
cgroup.subtree_control	io.pressure	     sys-kernel-config.mount
cgroup.threads		io.stat		     sys-kernel-debug.mount
cpu.pressure		lxc.pivot	     sys-kernel-tracing.mount
cpuset.cpus.effective	memory.numa_stat     system.slice
cpuset.mems.effective	memory.pressure      user.slice
cpu.stat		memory.stat

Ho hum :-/

   Julian


lxc-start debian-unstable-trial 20220511204109.279 INFO     lxccontainer - lxccontainer.c:do_lxcapi_start:987 - Set process title to [lxc monitor] /var/lib/lxc debian-unstable-trial
lxc-start debian-unstable-trial 20220511204109.280 DEBUG    lxccontainer - lxccontainer.c:wait_on_daemonized_start:848 - First child 502040 exited
lxc-start debian-unstable-trial 20220511204109.280 INFO     lsm - lsm/lsm.c:lsm_init_static:38 - Initialized LSM security driver AppArmor
lxc-start debian-unstable-trial 20220511204109.281 DEBUG    seccomp - seccomp.c:parse_config_v2:656 - Host native arch is [3221225534]
lxc-start debian-unstable-trial 20220511204109.281 INFO     seccomp - seccomp.c:parse_config_v2:807 - Processing "reject_force_umount  # comment this to allow umount -f;  not recommended"
lxc-start debian-unstable-trial 20220511204109.281 INFO     seccomp - seccomp.c:do_resolve_add_rule:524 - Set seccomp rule to reject force umounts
lxc-start debian-unstable-trial 20220511204109.281 INFO     seccomp - seccomp.c:do_resolve_add_rule:524 - Set seccomp rule to reject force umounts
lxc-start debian-unstable-trial 20220511204109.281 INFO     seccomp - seccomp.c:do_resolve_add_rule:524 - Set seccomp rule to reject force umounts
lxc-start debian-unstable-trial 20220511204109.281 INFO     seccomp - seccomp.c:parse_config_v2:807 - Processing "[all]"
lxc-start debian-unstable-trial 20220511204109.281 INFO     seccomp - seccomp.c:parse_config_v2:807 - Processing "kexec_load errno 1"
lxc-start debian-unstable-trial 20220511204109.281 INFO     seccomp - seccomp.c:do_resolve_add_rule:564 - Adding native rule for syscall[246:kexec_load] action[327681:errno] arch[0]
lxc-start debian-unstable-trial 20220511204109.281 INFO     seccomp - seccomp.c:do_resolve_add_rule:564 - Adding compat rule for syscall[246:kexec_load] action[327681:errno] arch[1073741827]
lxc-start debian-unstable-trial 20220511204109.281 INFO     seccomp - seccomp.c:do_resolve_add_rule:564 - Adding compat rule for syscall[246:kexec_load] action[327681:errno] arch[1073741886]
lxc-start debian-unstable-trial 20220511204109.281 INFO     seccomp - seccomp.c:parse_config_v2:807 - Processing "open_by_handle_at errno 1"
lxc-start debian-unstable-trial 20220511204109.281 INFO     seccomp - seccomp.c:do_resolve_add_rule:564 - Adding native rule for syscall[304:open_by_handle_at] action[327681:errno] arch[0]
lxc-start debian-unstable-trial 20220511204109.281 INFO     seccomp - seccomp.c:do_resolve_add_rule:564 - Adding compat rule for syscall[304:open_by_handle_at] action[327681:errno] arch[1073741827]
lxc-start debian-unstable-trial 20220511204109.281 INFO     seccomp - seccomp.c:do_resolve_add_rule:564 - Adding compat rule for syscall[304:open_by_handle_at] action[327681:errno] arch[1073741886]
lxc-start debian-unstable-trial 20220511204109.281 INFO     seccomp - seccomp.c:parse_config_v2:807 - Processing "init_module errno 1"
lxc-start debian-unstable-trial 20220511204109.281 INFO     seccomp - seccomp.c:do_resolve_add_rule:564 - Adding native rule for syscall[175:init_module] action[327681:errno] arch[0]
lxc-start debian-unstable-trial 20220511204109.281 INFO     seccomp - seccomp.c:do_resolve_add_rule:564 - Adding compat rule for syscall[175:init_module] action[327681:errno] arch[1073741827]
lxc-start debian-unstable-trial 20220511204109.281 INFO     seccomp - seccomp.c:do_resolve_add_rule:564 - Adding compat rule for syscall[175:init_module] action[327681:errno] arch[1073741886]
lxc-start debian-unstable-trial 20220511204109.281 INFO     seccomp - seccomp.c:parse_config_v2:807 - Processing "finit_module errno 1"
lxc-start debian-unstable-trial 20220511204109.281 INFO     seccomp - seccomp.c:do_resolve_add_rule:564 - Adding native rule for syscall[313:finit_module] action[327681:errno] arch[0]
lxc-start debian-unstable-trial 20220511204109.281 INFO     seccomp - seccomp.c:do_resolve_add_rule:564 - Adding compat rule for syscall[313:finit_module] action[327681:errno] arch[1073741827]
lxc-start debian-unstable-trial 20220511204109.281 INFO     seccomp - seccomp.c:do_resolve_add_rule:564 - Adding compat rule for syscall[313:finit_module] action[327681:errno] arch[1073741886]
lxc-start debian-unstable-trial 20220511204109.281 INFO     seccomp - seccomp.c:parse_config_v2:807 - Processing "delete_module errno 1"
lxc-start debian-unstable-trial 20220511204109.281 INFO     seccomp - seccomp.c:do_resolve_add_rule:564 - Adding native rule for syscall[176:delete_module] action[327681:errno] arch[0]
lxc-start debian-unstable-trial 20220511204109.281 INFO     seccomp - seccomp.c:do_resolve_add_rule:564 - Adding compat rule for syscall[176:delete_module] action[327681:errno] arch[1073741827]
lxc-start debian-unstable-trial 20220511204109.281 INFO     seccomp - seccomp.c:do_resolve_add_rule:564 - Adding compat rule for syscall[176:delete_module] action[327681:errno] arch[1073741886]
lxc-start debian-unstable-trial 20220511204109.281 INFO     seccomp - seccomp.c:parse_config_v2:1017 - Merging compat seccomp contexts into main context
lxc-start debian-unstable-trial 20220511204109.511 INFO     start - start.c:lxc_init:883 - Container "debian-unstable-trial" is initialized
lxc-start debian-unstable-trial 20220511204109.531 INFO     cgfsng - cgroups/cgfsng.c:cgfsng_monitor_create:1028 - The monitor process uses "lxc.monitor.debian-unstable-trial" as cgroup
lxc-start debian-unstable-trial 20220511204109.531 DEBUG    storage - storage/storage.c:get_storage_by_name:209 - Detected rootfs type "dir"
lxc-start debian-unstable-trial 20220511204109.532 INFO     cgfsng - cgroups/cgfsng.c:cgfsng_payload_create:1136 - The container process uses "lxc.payload.debian-unstable-trial" as inner and "lxc.payload.debian-unstable-trial" as limit cgroup
lxc-start debian-unstable-trial 20220511204109.534 INFO     start - start.c:lxc_spawn:1759 - Cloned CLONE_NEWNS
lxc-start debian-unstable-trial 20220511204109.534 INFO     start - start.c:lxc_spawn:1759 - Cloned CLONE_NEWPID
lxc-start debian-unstable-trial 20220511204109.534 INFO     start - start.c:lxc_spawn:1759 - Cloned CLONE_NEWUTS
lxc-start debian-unstable-trial 20220511204109.534 INFO     start - start.c:lxc_spawn:1759 - Cloned CLONE_NEWIPC
lxc-start debian-unstable-trial 20220511204109.534 INFO     start - start.c:lxc_spawn:1759 - Cloned CLONE_NEWNET
lxc-start debian-unstable-trial 20220511204109.534 DEBUG    start - start.c:lxc_try_preserve_namespace:139 - Preserved mnt namespace via fd 21 and stashed path as mnt:/proc/502041/fd/21
lxc-start debian-unstable-trial 20220511204109.534 DEBUG    start - start.c:lxc_try_preserve_namespace:139 - Preserved pid namespace via fd 22 and stashed path as pid:/proc/502041/fd/22
lxc-start debian-unstable-trial 20220511204109.534 DEBUG    start - start.c:lxc_try_preserve_namespace:139 - Preserved uts namespace via fd 23 and stashed path as uts:/proc/502041/fd/23
lxc-start debian-unstable-trial 20220511204109.534 DEBUG    start - start.c:lxc_try_preserve_namespace:139 - Preserved ipc namespace via fd 24 and stashed path as ipc:/proc/502041/fd/24
lxc-start debian-unstable-trial 20220511204109.534 DEBUG    start - start.c:lxc_try_preserve_namespace:139 - Preserved net namespace via fd 25 and stashed path as net:/proc/502041/fd/25
lxc-start debian-unstable-trial 20220511204109.534 INFO     cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits_legacy:2749 - Limits for the legacy cgroup hierarchies have been setup
lxc-start debian-unstable-trial 20220511204109.534 WARN     cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits:2809 - Invalid argument - Ignoring cgroup2 limits on legacy cgroup system
lxc-start debian-unstable-trial 20220511204109.534 INFO     start - start.c:do_start:1206 - Unshared CLONE_NEWCGROUP
lxc-start debian-unstable-trial 20220511204109.542 INFO     network - network.c:netdev_configure_server_veth:655 - Retrieved mtu 1500 from lxcbr0
lxc-start debian-unstable-trial 20220511204109.557 INFO     network - network.c:netdev_configure_server_veth:720 - Attached "vethS9TtPh" to bridge "lxcbr0"
lxc-start debian-unstable-trial 20220511204109.557 DEBUG    network - network.c:netdev_configure_server_veth:851 - Instantiated veth tunnel "vethS9TtPh <--> vethVbX9aI"
lxc-start debian-unstable-trial 20220511204109.558 DEBUG    conf - conf.c:lxc_mount_rootfs:1423 - Mounted rootfs "/var/lib/lxc/debian-unstable-trial/rootfs" onto "/usr/lib/x86_64-linux-gnu/lxc/rootfs" with options "(null)"
lxc-start debian-unstable-trial 20220511204109.558 INFO     conf - conf.c:setup_utsname:866 - Set hostname to "debian-unstable-trial"
lxc-start debian-unstable-trial 20220511204109.558 INFO     network - network.c:lxc_setup_network_in_child_namespaces:4005 - Finished setting up network devices with caller assigned names
lxc-start debian-unstable-trial 20220511204109.583 DEBUG    network - network.c:setup_hw_addr:3807 - Mac address "00:16:3e:98:ce:14" on "eth0" has been setup
lxc-start debian-unstable-trial 20220511204109.583 DEBUG    network - network.c:lxc_network_setup_in_child_namespaces_common:3948 - Network device "eth0" has been setup
lxc-start debian-unstable-trial 20220511204109.583 INFO     network - network.c:lxc_setup_network_in_child_namespaces:4021 - Finished setting up network devices with kernel assigned names
lxc-start debian-unstable-trial 20220511204109.583 INFO     conf - conf.c:mount_autodev:1206 - Preparing "/dev"
lxc-start debian-unstable-trial 20220511204109.583 INFO     conf - conf.c:mount_autodev:1267 - Prepared "/dev"
lxc-start debian-unstable-trial 20220511204109.583 DEBUG    conf - conf.c:lxc_mount_auto_mounts:733 - Invalid argument - Tried to ensure procfs is unmounted
lxc-start debian-unstable-trial 20220511204109.584 DEBUG    conf - conf.c:lxc_mount_auto_mounts:756 - Invalid argument - Tried to ensure sysfs is unmounted
lxc-start debian-unstable-trial 20220511204109.584 DEBUG    conf - conf.c:mount_entry:2403 - Remounting "/sys/fs/fuse/connections" on "/usr/lib/x86_64-linux-gnu/lxc/rootfs/sys/fs/fuse/connections" to respect bind or remount options
lxc-start debian-unstable-trial 20220511204109.584 DEBUG    conf - conf.c:mount_entry:2422 - Flags for "/sys/fs/fuse/connections" were 4110, required extra flags are 14
lxc-start debian-unstable-trial 20220511204109.584 DEBUG    conf - conf.c:mount_entry:2466 - Mounted "/sys/fs/fuse/connections" on "/usr/lib/x86_64-linux-gnu/lxc/rootfs/sys/fs/fuse/connections" with filesystem type "none"
lxc-start debian-unstable-trial 20220511204109.584 DEBUG    conf - conf.c:mount_entry:2466 - Mounted "proc" on "/usr/lib/x86_64-linux-gnu/lxc/rootfs/dev/.lxc/proc" with filesystem type "proc"
lxc-start debian-unstable-trial 20220511204109.584 DEBUG    conf - conf.c:mount_entry:2466 - Mounted "sys" on "/usr/lib/x86_64-linux-gnu/lxc/rootfs/dev/.lxc/sys" with filesystem type "sysfs"
lxc-start debian-unstable-trial 20220511204109.584 INFO     conf - conf.c:run_script_argv:337 - Executing script "/usr/share/lxcfs/lxc.mount.hook" for container "debian-unstable-trial", config section "lxc"
lxc-start debian-unstable-trial 20220511204109.652 INFO     conf - conf.c:lxc_fill_autodev:1304 - Populating "/dev"
lxc-start debian-unstable-trial 20220511204109.652 DEBUG    conf - conf.c:lxc_fill_autodev:1313 - Created device node "full"
lxc-start debian-unstable-trial 20220511204109.652 DEBUG    conf - conf.c:lxc_fill_autodev:1313 - Created device node "null"
lxc-start debian-unstable-trial 20220511204109.652 DEBUG    conf - conf.c:lxc_fill_autodev:1313 - Created device node "random"
lxc-start debian-unstable-trial 20220511204109.652 DEBUG    conf - conf.c:lxc_fill_autodev:1313 - Created device node "tty"
lxc-start debian-unstable-trial 20220511204109.652 DEBUG    conf - conf.c:lxc_fill_autodev:1313 - Created device node "urandom"
lxc-start debian-unstable-trial 20220511204109.652 DEBUG    conf - conf.c:lxc_fill_autodev:1313 - Created device node "zero"
lxc-start debian-unstable-trial 20220511204109.652 INFO     conf - conf.c:lxc_fill_autodev:1392 - Populated "/dev"
lxc-start debian-unstable-trial 20220511204109.652 INFO     conf - conf.c:lxc_transient_proc:3757 - Caller's PID is 1; /proc/self points to 1
lxc-start debian-unstable-trial 20220511204109.652 DEBUG    conf - conf.c:lxc_setup_devpts_child:1738 - Attached detached devpts mount 24 to 22/pts
lxc-start debian-unstable-trial 20220511204109.652 DEBUG    conf - conf.c:lxc_setup_devpts_child:1824 - Created "/dev/ptmx" file as bind mount target
lxc-start debian-unstable-trial 20220511204109.652 DEBUG    conf - conf.c:lxc_setup_devpts_child:1831 - Bind mounted "/dev/pts/ptmx" to "/dev/ptmx"
lxc-start debian-unstable-trial 20220511204109.652 DEBUG    conf - conf.c:lxc_allocate_ttys:1092 - Created tty with ptx fd 26 and pty fd 27 and index 1
lxc-start debian-unstable-trial 20220511204109.652 DEBUG    conf - conf.c:lxc_allocate_ttys:1092 - Created tty with ptx fd 28 and pty fd 29 and index 2
lxc-start debian-unstable-trial 20220511204109.652 DEBUG    conf - conf.c:lxc_allocate_ttys:1092 - Created tty with ptx fd 30 and pty fd 31 and index 3
lxc-start debian-unstable-trial 20220511204109.652 DEBUG    conf - conf.c:lxc_allocate_ttys:1092 - Created tty with ptx fd 32 and pty fd 33 and index 4
lxc-start debian-unstable-trial 20220511204109.652 INFO     conf - conf.c:lxc_allocate_ttys:1097 - Finished creating 4 tty devices
lxc-start debian-unstable-trial 20220511204109.652 DEBUG    conf - conf.c:lxc_setup_ttys:1056 - Bind mounted "" onto "tty1"
lxc-start debian-unstable-trial 20220511204109.652 DEBUG    conf - conf.c:lxc_setup_ttys:1056 - Bind mounted "" onto "tty2"
lxc-start debian-unstable-trial 20220511204109.652 DEBUG    conf - conf.c:lxc_setup_ttys:1056 - Bind mounted "" onto "tty3"
lxc-start debian-unstable-trial 20220511204109.652 DEBUG    conf - conf.c:lxc_setup_ttys:1056 - Bind mounted "" onto "tty4"
lxc-start debian-unstable-trial 20220511204109.653 INFO     conf - conf.c:lxc_setup_ttys:1063 - Finished setting up 4 /dev/tty<N> device(s)
lxc-start debian-unstable-trial 20220511204109.654 INFO     conf - conf.c:setup_personality:1904 - Set personality to "0lx0"
lxc-start debian-unstable-trial 20220511204109.654 DEBUG    conf - conf.c:capabilities_deny:3187 - Dropped mac_admin (33) capability
lxc-start debian-unstable-trial 20220511204109.654 DEBUG    conf - conf.c:capabilities_deny:3187 - Dropped mac_override (32) capability
lxc-start debian-unstable-trial 20220511204109.654 DEBUG    conf - conf.c:capabilities_deny:3187 - Dropped sys_time (25) capability
lxc-start debian-unstable-trial 20220511204109.654 DEBUG    conf - conf.c:capabilities_deny:3187 - Dropped sys_module (16) capability
lxc-start debian-unstable-trial 20220511204109.654 DEBUG    conf - conf.c:capabilities_deny:3187 - Dropped sys_rawio (17) capability
lxc-start debian-unstable-trial 20220511204109.654 DEBUG    conf - conf.c:capabilities_deny:3190 - Capabilities have been setup
lxc-start debian-unstable-trial 20220511204109.654 NOTICE   conf - conf.c:lxc_setup:4450 - The container "debian-unstable-trial" is set up
lxc-start debian-unstable-trial 20220511204109.654 INFO     apparmor - lsm/apparmor.c:apparmor_process_label_set_at:1186 - Set AppArmor label to "lxc-debian-unstable-trial_</var/lib/lxc>//&:lxc-debian-unstable-trial_<-var-lib-lxc>:"
lxc-start debian-unstable-trial 20220511204109.654 INFO     apparmor - lsm/apparmor.c:apparmor_process_label_set:1231 - Changed AppArmor profile to lxc-debian-unstable-trial_</var/lib/lxc>//&:lxc-debian-unstable-trial_<-var-lib-lxc>:
lxc-start debian-unstable-trial 20220511204109.655 WARN     cgfsng - cgroups/cgfsng.c:get_hierarchy:142 - There is no useable devices controller
lxc-start debian-unstable-trial 20220511204109.655 ERROR    cgfsng - cgroups/cgfsng.c:cg_legacy_set_data:2675 - No such file or directory - Failed to setup limits for the "devices" controller. The controller seems to be unused by "cgfsng" cgroup driver or not enabled on the cgroup hierarchy
lxc-start debian-unstable-trial 20220511204109.655 ERROR    cgfsng - cgroups/cgfsng.c:cgfsng_setup_limits_legacy:2742 - No such file or directory - Failed to set "devices.deny" to "a"
lxc-start debian-unstable-trial 20220511204109.655 ERROR    start - start.c:lxc_spawn:1890 - Failed to setup legacy device cgroup controller limits
lxc-start debian-unstable-trial 20220511204109.655 DEBUG    network - network.c:lxc_delete_network:4159 - Deleted network devices
lxc-start debian-unstable-trial 20220511204109.655 ERROR    lxccontainer - lxccontainer.c:wait_on_daemonized_start:867 - Received container state "ABORTING" instead of "RUNNING"
lxc-start debian-unstable-trial 20220511204109.655 ERROR    lxc_start - tools/lxc_start.c:main:306 - The container failed to start
lxc-start debian-unstable-trial 20220511204109.655 ERROR    lxc_start - tools/lxc_start.c:main:309 - To get more details, run the container in foreground mode
lxc-start debian-unstable-trial 20220511204109.655 ERROR    lxc_start - tools/lxc_start.c:main:311 - Additional information can be obtained by setting the --logfile and --logpriority options
lxc-start debian-unstable-trial 20220511204109.655 ERROR    start - start.c:__lxc_start:2068 - Failed to spawn container "debian-unstable-trial"
lxc-start debian-unstable-trial 20220511204109.655 WARN     start - start.c:lxc_abort:1038 - No such process - Failed to send SIGKILL via pidfd 20 for process 502047
lxc-start debian-unstable-trial 20220511204109.900 INFO     conf - conf.c:run_script_argv:337 - Executing script "/usr/share/lxcfs/lxc.reboot.hook" for container "debian-unstable-trial", config section "lxc"

[toc] | [prev] | [next] | [standalone]

#1105081 — Bug#1010469: Bug#1010437: autopkgtest: autopkgtest-build-lxc fails to build working lxc environment

tags 1010469 unreproducible
fixed 1010469 1:4.0.11-1
thanks

On Wed, May 11, 2022 at 03:03:54PM -0300, Antonio Terceiro wrote:
> 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?
> > [...]

I decided to reinstall my system from scratch, and now this bug has
gone away.  So as no-one else could reproduce it and I have no idea
what has changed on my system as a result of reinstalling, I'm closing
it with an "unreproducible" tag.

Thanks for your help along the way!

Best wishes,

   Julian

[toc] | [prev] | [next] | [standalone]

#1105851 — Bug#1010469: Bug#1010437: autopkgtest: autopkgtest-build-lxc fails to build working lxc environment

notfixed 1010469 1:4.0.11-1
thanks

> I decided to reinstall my system from scratch, and now this bug has
> gone away.  So as no-one else could reproduce it and I have no idea
> what has changed on my system as a result of reinstalling, I'm closing
> it with an "unreproducible" tag.

Oh dear, oh dear, oh dear.  It's just happened again.

I am so completely stumped by this one.

   Julian

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web