Description

After the upgrade to Fedora-43, I see a weird runc behavior. We also see it in the https://github.com/containers/conmon CI.

The container is created and the runc status shows it is in a created state. Next call of runc start fails with cannot start a container that has stopped and next calls of runc status shows the container is in the stopped state despite the fact nothing else started it.

The very same CI tests worked well before. You can see the issue with more debugging logs in the containers/conmon#643 - check the Build CI job in cirrus-ci.

Steps to reproduce the issue

1. Clone the https://github.com/containers/conmon.git
2. Build it using make and run the tests using make test on Fedora-43.
3. The tests fail.

Describe the results you received and expected

Previously, the containers were started without any issues in this situation. Now the runc start fails with cannot start a container that has stopped.

What version of runc are you using?

runc-1.4.0-1.fc43.x86_64

Host OS information

NAME="Fedora Linux"
VERSION="43 (Workstation Edition)"
RELEASE_TYPE=stable
ID=fedora
VERSION_ID=43
VERSION_CODENAME=""
PRETTY_NAME="Fedora Linux 43 (Workstation Edition)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:43"
DEFAULT_HOSTNAME="fedora"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f43/"
SUPPORT_URL="https://ask.fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=43
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=43
SUPPORT_END=2026-12-02
VARIANT="Workstation Edition"
VARIANT_ID=workstation

Host kernel information

Linux fedora 6.18.8-200.fc43.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Jan 30 20:23:28 UTC 2026 x86_64 GNU/Linux