Lifecycle guide for conmon from container

All releases, patches, maintenance and support periods at a glance

All supported products Free Versio.io trial

📅 Last update on 2026-04-16

What is conmon?

Automate product release and end-of-life management

An OCI container runtime monitor.Conmon is a monitoring program and communication tool between a container manager (like Podman or CRI-O) and an OCI runtime (like runc or crun) for a single container.Upon being launched, conmon (usually) double-forks to daemonize and detach from the parent that launched it. It then launches the runtime as its child. This allows managing processes to die in the foreground, but still be able to watch over and connect to the child process (the container).While the container runs, conmon does two things:* Provides a socket for attaching to the container, holding open the container"s standard streams and forwarding them over the socket.* Writes the contents of the container"s streams to a log file (or to the systemd journal) so they can be read after the container"s death.Finally, upon the containers death, conmon will record its exit time and code to be read by the managing programs.

The entire lifecycle of conmon

The following figure shows you the visualised product life cycle of conmon. You can see all releases with the latest patch version, the long-term support characteristics (orange flag in the green circle, the periods for version provision, maintenance and support.