Package: runc Version: 1.1.5+ds1-1+deb12u1 Severity: normal Dear Maintainer,
runc in bookworm has a bug where runc corrupts the CpusetCpus mask sent to systemd. This results in the container pinned to unexpected CPUs. This affects Docker's --cpuset-cpus flag. Upstream fixed this important issue in https://github.com/opencontainers/runc/commit/77cae9addc0c7c9ef52513b4e46b2e6485e4e469. Could the fix be backported to bookworm? -- System Information: Debian Release: 12.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-22-cloud-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages runc depends on: ii libc6 2.36-9+deb12u7 ii libseccomp2 2.5.4-1+deb12u1 Versions of packages runc recommends: ii criu 3.17.1-2 runc suggests no packages. -- no debconf information
