[pkg-lxc-devel] Bug#977923: lxc: start fails on Linux 5.10: Failed to copy "/proc/self/mountinfo"
terceiro at debian.org
Tue Dec 22 23:42:15 GMT 2020
Control: tag -1 + confirmed fixed-upstream
Control: forwarded -1 https://github.com/lxc/lxc/issues/3580
On Tue, Dec 22, 2020 at 04:04:06PM -0700, Kevin Locke wrote:
> Package: lxc
> Version: 1:4.0.4-6
> Severity: normal
> Dear Maintainer,
> A freshly created container with Debian testing runs fine on Linux 5.9
> (from linux-image-5.9.0-4-amd64 5.9.11-1), but fails to start on Linux
> 5.10 (from linux-image-5.10.0-trunk-amd64 5.10.1-1~exp1). To reproduce:
> lxc-create -n testing-amd64 -t debian -- --release testing
> lxc-start -n testing-amd64 --logfile debug.log --logpriority TRACE
> Works fine on 5.9, prints the following on 5.10:
> lxc-start: testing-amd64: lxccontainer.c: wait_on_daemonized_start: 849 Received container state "ABORTING" instead of "RUNNING"
> lxc-start: testing-amd64: tools/lxc_start.c: main: 308 The container failed to start
> lxc-start: testing-amd64: tools/lxc_start.c: main: 311 To get more details, run the container in foreground mode
> lxc-start: testing-amd64: tools/lxc_start.c: main: 313 Additional information can be obtained by setting the --logfile and --logpriority options
> The first error in debug.log is:
> lxc-start testing-amd64 20201222225630.248 ERROR conf - conf.c:turn_into_dependent_mounts:2965 - Invalid argument - Failed to copy "/proc/self/mountinfo"
> debug.log attached.
I have been seeing this as well, but I have been too lazy to debug it
myself. Thanks for your bug report.
I'm trying the upstream fix -- which
is quite recent -- here.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 833 bytes
Desc: not available
More information about the Pkg-lxc-devel