What were you trying to do that didn't work?

I was using podman quadlets to run containerized services and after a recent update many containers (ones using catatonit) started experiencing SIGSEGV on startup.

What is the impact of this issue to you?

I was unable to run some of the core services I had been running on my server.

Please provide the package NVR for which the bug is seen:

root@cloud:~# dnf info catatonit-5:0.2.1-3.el10.x86_64
Last metadata expiration check: 1:53:47 ago on Wed 04 Mar 2026 03:31:48 PM CET.
Available Packages
Name         : catatonit
Epoch        : 5
Version      : 0.2.1
Release      : 3.el10
Architecture : x86_64
Size         : 316 k
Source       : catatonit-0.2.1-3.el10.src.rpm
Repository   : appstream
Summary      : A signal-forwarding process manager for containers
URL          : https://github.com/openSUSE/catatonit
License      : GPL-3.0-or-later
Description  : Catatonit is a /usr/sbin/init program for use within containers. It
             : forwards (almost) all signals to the spawned child, tears down
             : the container when the spawned child exits, and otherwise
             : cleans up other exited processes (zombies).
             : 
             : This is a reimplementation of other container init programs (such as
             : "tini" or "dumb-init"), but uses modern Linux facilities (such as
             : signalfd(2)) and has no additional features.

How reproducible is this bug?:

I can reproduce it on any recently updated CentOS Stream 10 system I have tried it on

Steps to reproduce

1. Install catatonit 5:0.2.1-3.el10
2. Run `/usr/libexec/podman/catatonit – /bin/echo test

Expected results

The text `test` is output to the console

Actual results

Segmentation fault (core dumped)

Workaround:

I was able to install the earlier `catatonit-5:0.2.1-1.el10.x86_64` and create a soft link from `/usr/libexec/catatonit/catatonit` to `/usr/libexec/podman/catatonit`.