Description

We have a set of devices which have recently changed behavior. Starting with v1.3.1 and confirmed again on v1.3.2, docker exec no longer works, instead returning

OCI runtime exec failed: exec failed: unable to start container process: error writing config to pipe: write init-p: broken pipe: unknown

Steps to reproduce the issue

1. Start any container - e.g. docker run -it --name deleteme --rm debian:trixie-slim
2. After container is started, in another window run docker exec deleteme echo hello
   • this fails with "OCI runtime exec failed: exec failed"

Describe the results you received and expected

hello should be printed by `docker exec deleteme echo hello

What version of runc are you using?

runc version 1.3.1-1
commit: e6457af
spec: 1.2.1
go: go1.25.1
libseccomp: 2.5.4

Additional info

• According to dpkg, runc is provided by moby-runc Debian package.
• Running apt-cache policy moby-run shows that the installed version comes from

  *** 1.3.1-debian12u1 500
        500 https://packages.microsoft.com/debian/12/prod bookworm/main arm64 Packages
        100 /var/lib/dpkg/status
  

Host OS information

PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

Host kernel information

Linux iotg-imx8plus-1250227001754 6.1.55-compulab-imx8plus #99054 SMP PREEMPT Fri Sep 6 20:52:51 UTC 2024 aarch64 GNU/Linux