[pkg-lxc-devel] Bug#1116615: Unprivileged containers using veth have stopped working after upgrading from bookworm to trixie

Linas Vepstas linasvepstas at gmail.com
Mon Sep 29 07:32:01 BST 2025


Package: lxc
Version: 1:6.0.4-4+b3

Unprivileged lxc containers using veth will not start after upgrade
from bookworm to trixie. Details are given in
https://github.com/lxc/lxc/issues/4587  They do start just fine, when
the Debian  executable `lxc-user-nic` is replaced by one built from
today's github code. That is: what's in github right now works. What's
in Debian trixie doesn't.

The details are in the github bug report. To summarize, the errors I
was seeing were these:

lxc-start -F mycontainer
lxc-start: mycontainer: ../src/lxc/network.c:
lxc_create_network_unpriv_exec: 3029 lxc-user-nic failed to configure
requested network: ../src/lxc/cmd/lxc_user_nic.c: 838:
lxc_secure_rename_in_ns - Permission denied - Failed opening network
namespace path for 383865
../src/lxc/cmd/lxc_user_nic.c: 1219: main: Failed to rename the link
lxc-start: mycontainer: ../src/lxc/start.c: lxc_spawn: 1852 Failed to
create the network
lxc-start: mycontainer: ../src/lxc/start.c: __lxc_start: 2119 Failed
to spawn container "mycontainer"

-- Linas

-- 
Patrick: Are they laughing at us?
Sponge Bob: No, Patrick, they are laughing next to us.



More information about the Pkg-lxc-devel mailing list