Dear Lxc team,
Im am trying to start one container with Debian Trixie (13.1) on one
host (hn-nanopir4s-1000) running Debian 13.1.
Host is one arm64 target (nanopir4s) and current lxc is :
ansible@hn-nanopir4s-1000:~$ sudo lxc-ls --version
6.0.4
ansible@hn-nanopir4s-1000:~$ uname -a
Linux hn-nanopir4s-1000 6.12.44-current-rockchip64 #1 SMP PREEMPT Thu Aug 28 14:31:16 UTC 2025 aarch64 GNU/Linux
ansible@hn-nanopir4s-1000:~$ cat /etc/debian_version
13.1
Target is booted with cgroupV2 options
ansible@hn-nanopir4s-1000:~$ cat /proc/cmdline
root=UUID=ce00bdc0-6d0c-4958-874c-e95bf0ddc8a8 rootwait rootfstype=ext4 console=ttyS2,1500000 consoleblank=0 loglevel=7 ubootpart=646b52f2-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u apparmor=0 selinux=0 cgroup_no_v1=all cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1
ansible@hn-nanopir4s-1000:~$
… and cgroupv2 are mouted
ansible@hn-nanopir4s-1000:~$ mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime,hidepid=invisible)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=1896640k,nr_inodes=474160,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=600,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=394508k,mode=755)
/dev/mmcblk1p1 on / type ext4 (rw,noatime,nodiratime,errors=remount-ro,commit=120)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
securityfs on /sys/kernel/security type securityfs (rw,relatime)
pstore on /sys/fs/pstore type pstore (rw,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=789000k)
none on /sys/kernel/config type configfs (rw,relatime)
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime)
tmpfs on /tmp type tmpfs (rw,nosuid,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
ansible@hn-nanopir4s-1000:~$
Configuration file (partial) is …
ansible@hn-nanopir4s-1000:~$ sudo cat /etc/lxc/auto/vn-debian-arm64-1000 |grep -v “#” |grep -v ^$ |head -10
lxc.arch = aarch64
lxc.utsname = vn-debian-arm64-1000
lxc.start.auto = 1
lxc.start.order = 20
lxc.start.delay = 0
lxc.group = grp_lxc_start_on_boot
lxc.init_cmd = /sbin/init
lxc.ephemeral = 0
lxc.loglevel = DEBUG
lxc.logfile = /var/log/lxc/vn-debian-arm64-1000.log
Please note that this configuration was ok on previous Debian release
12 (Bookworm) with following lxc tools on the same architecture
(arm64), because on one another target, i have…
ansible@hn-rock64-130:~$ sudo lxc-ls --version
5.0.2
ansible@hn-rock64-130:~$ cat /etc/debian_version
12.12
ansible@hn-rock64-130:~$ uname -a
Linux hn-rock64-130 6.12.30+bpo-arm64 #1 SMP Debian 6.12.30-1~bpo12+1 (2025-06-14) aarch64 GNU/Linux
ansible@hn-rock64-130:~$
ansible@hn-rock64-130:~$ sudo lxc-ls -f
NAME STATE AUTOSTART GROUPS IPV4 IPV6 UNPRIVILEGED
vn-bookworm-arm64-130 RUNNING 1 grp_lxc_start_on_boot 192.168.51.118, 192.168.54.118, 192.168.56.118, 192.168.57.118 - false
vn-bullseye-arm64-130 RUNNING 1 grp_lxc_start_on_boot 192.168.54.117, 192.168.56.117, 192.168.57.117 - false
vn-buster-arm64-130 RUNNING 1 grp_lxc_start_on_boot 192.168.54.114, 192.168.56.114, 192.168.57.114 - false
vn-debian-arm64-130 RUNNING 1 grp_lxc_start_on_boot 192.168.51.115, 192.168.54.115, 192.168.56.115, 192.168.57.115 - false
vn-ntp-130 RUNNING 1 grp_lxc_start_on_boot 192.168.54.116, 192.168.55.116, 192.168.57.116 - false
ansible@hn-rock64-130:~$
ansible@hn-rock64-130:~$ sudo cat /etc/lxc/auto/vn-debian-arm64-130 |grep -v “#” |grep -v ^$ |head -15
lxc.arch = aarch64
lxc.uts.name = vn-debian-arm64-130
lxc.start.auto = 1
lxc.start.order = 20
lxc.start.delay = 0
lxc.group = grp_lxc_start_on_boot
lxc.init.cmd = /sbin/init
lxc.init.uid = 0
lxc.init.gid = 0
lxc.ephemeral = 0
lxc.console.buffer.size = 102400
lxc.console.size = 102400
lxc.log.level = DEBUG
lxc.log.file = /var/log/lxc/vn-debian-arm64-130.log
ansible@hn-rock64-130:~$
ALL is OK on target hn-rock64-130… but on hn-nanopir4s-1000
When a start container …
ansible@hn-nanopir4s-1000:~$ sudo lxc-start -n vn-debian-arm64-1000 -f /etc/lxc/auto/vn-debian-arm64-1000
lxc-start: vn-debian-arm64-1000: ../src/lxc/confile.c: set_config_unsupported_key: 164 Invalid argument - Unsupported config key “lxc.utsname”
lxc-start: vn-debian-arm64-1000: ../src/lxc/parse.c: lxc_file_for_each_line_mmap: 129 Failed to parse config file “/var/lib/lxc/vn-debian-arm64-1000/config” at line “lxc.utsname = vn-debian-arm64-1000”
Thanks in advance to help me to clarify why lxc.utsname seems to
change in the new version of lxc 6.x ?
I have remove (comment) this parameter into configuration file, and
when trying to restart, i have now…
ansible@hn-nanopir4s-1000:~$ sudo sed -i -e ‘s/lxc.utsname/LXC.utsname/g’ /etc/lxc/auto/vn-debian-arm64-1000
ansible@hn-nanopir4s-1000:~$
and now …
ansible@hn-nanopir4s-1000:~$ sudo lxc-start -n vn-debian-arm64-1000 -f /etc/lxc/auto/vn-debian-arm64-1000
lxc-start: vn-ntp-1000: ../src/lxc/confile.c: set_config_unsupported_key: 164 Invalid argument - Unsupported config key “lxc.init_cmd”
lxc-start: vn-ntp-1000: ../src/lxc/parse.c: lxc_file_for_each_line_mmap: 129 Failed to parse config file “/var/lib/lxc/vn-ntp-1000/config” at line “lxc.init_cmd = /sbin/init”
Failed to load config for vn-ntp-1000
lxc-start: vn-ntp-1000: ../src/lxc/tools/lxc_start.c: lxc_start_main: 207 Failed to create lxc_container
ansible@hn-nanopir4s-1000:~$
ansible@hn-nanopir4s-1000:~$ sudo sed -i -e ‘s/lxc.init_cmd/LXC.init_cmd/g’ /etc/lxc/auto/vn-debian-arm64-1000
ansible@hn-nanopir4s-1000:~$ sudo lxc-start -n vn-debian-arm64-1000 -f /etc/lxc/auto/vn-debian-arm64-1000
lxc-start: vn-debian-arm64-1000: ../src/lxc/confile.c: set_config_unsupported_key: 164 Invalid argument - Unsupported config key “lxc.loglevel”
lxc-start: vn-debian-arm64-1000: ../src/lxc/parse.c: lxc_file_for_each_line_mmap: 129 Failed to parse config file “/var/lib/lxc/vn-debian-arm64-1000/config” at line “lxc.loglevel = DEBUG”
Failed to load config for vn-debian-arm64-1000
lxc-start: vn-debian-arm64-1000: ../src/lxc/tools/lxc_start.c: lxc_start_main: 207 Failed to create lxc_container
ansible@hn-nanopir4s-1000:~$