[pkg-lxc-devel] Bug#1119654: Bug#1119654: lxc-start --define lxc.mount.entry doesn't seem to work anymore on loong64
Mathias Gibbens
gibmat at debian.org
Fri Dec 26 18:25:44 GMT 2025
control: tags -1 + moreinfo
Hi Paul,
On Mon, 2025-11-03 at 21:50 +0100, Paul Gevers wrote:
> On Wed, 29 Oct 2025 22:42:54 +0100 Paul Gevers <elbrus at debian.org>
> wrote:
> > It seems that since very recently, the lxc containers for
> > ci.debian.net on loong64 (sid) don't mount the shared directory
> > anymore that autopkgtest needs and configures.
>
> Weirdly enough it seems to work now.
>
> I have a hypothesis. /tmp i[s] on tmpfs. Normally my /var/lib/lxc is
> also on tmpfs but when I tested the above, it may not have been so.
> Could that be a reason why the mount failed?
Have you seen this issue recur? I don't regularly run lxc containers
myself, but if tmpfs was an issue I would expect to see the issue on
other architectures.
loong64 is still pretty new; could a new kernel have introduced a
syscall or some other change that might require an update in lxc?
Mathias
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-lxc-devel/attachments/20251226/70b5f30b/attachment-0001.sig>
More information about the Pkg-lxc-devel
mailing list