The Podman and Fedora Quality teams are calling on users to help test a Rust-based rewrite of conmon, the low-level container monitor that runs underneath Podman, during a week-long testing event running Monday, October 12 through Sunday, October 18, 2026.
The exercise centres on what the project refers to as conmon v3, a version of the container monitor written in Rust, as announced in a post on Fedora Magazine. Podman itself is written in Go, but conmon — the small daemon responsible for supervising a running container, forwarding its logs, and handling events — has historically been written in C. The Rust rewrite aims to bring the memory-safety guarantees of Rust to that component, an infrastructure layer that, while largely invisible to end users, is critical to keeping containers running correctly.
Why conmon matters more than it appears to
For DevOps teams running Podman in production, conmon is the kind of dependency that rarely appears on a change-management ticket until something goes wrong. Its role means bugs there can surface as orphaned processes, lost container logs, or containers that fail to shut down cleanly — failures that can be difficult to trace back to a component most users never see. A rewrite in Rust, which eliminates whole classes of memory errors at compile time, is intended to reduce that class of failure, though the Fedora teams are treating the new version as untested and explicitly seeking user feedback before it moves closer to wider adoption.
What the test week is asking for
The test week is structured as a hands-on trial rather than a bug-hunt contest. Organisers are asking existing Podman users to run the same containers and commands they normally use — with conmon v3 installed — and compare the results against what they get with the current version. That kind of side-by-side comparison is precisely what a rewrite of this kind needs: performance regressions and behavioural differences tend to be subtle, and they are most easily caught by people whose workloads are already well understood.
What it means for adopters
The rewrite also sits within a broader shift across open-source infrastructure. Language teams have moved major systems components away from C in recent years, motivated by recurring memory-safety vulnerabilities in widely deployed software. Rust is a recurring answer in that discussion, and conmon is a relatively early example of the approach reaching the container runtime layer rather than the more visible application frameworks.
For organisations weighing Rust adoption, Podman's decision offers a useful data point: a rewrite of a critical but modest component, tested in the open, with users invited to validate it rather than simply accept it.
Interested participants can find sign-up details on the Fedora Project's Test Days pages and join the discussion during the week of October 12–18, 2026.
Podman 及 Fedora 品質團隊呼籲用戶協助測試以 Rust 重寫的 conmon，即在 Podman 底層運作的低層容器監控器。測試活動為期一週，由 2026 年 10 月 12 日（星期一）至 10 月 18 日（星期日）舉行。
是次活動集中於項目所稱的 conmon v3，即以 Rust 編寫的容器監控器版本，已在 Fedora Magazine 的一篇文章中公布。Podman 本身以 Go 編寫，而 conmon —— 這個負責監督執行中容器、轉發日誌及處理事件的小型 daemon —— 過往一直以 C 編寫。是次以 Rust 重寫，旨在將 Rust 的記憶體安全保證引入該組件。這層基建雖然對最終用戶幾乎不可見，卻是確保容器正確運作的關鍵。
為何 conmon 比表面看來更重要
對於在生產環境執行 Podman 的 DevOps 團隊而言，conmon 屬於那類很少會在變更管理工單上出現、直至出了問題才被提及的依賴項。正因其角色，該處的 bug 可能會呈現為孤立的進程、遺失的容器日誌，或無法正常關閉的容器 —— 而這類故障往往難以追溯至一個大多數用戶從未見過的組件。以 Rust 重寫，可在編譯時消除整類記憶體錯誤，目的正是減少此類故障。不過 Fedora 團隊視新版本為尚未經測試，並明確徵求用戶意見，方會逐步擴大採用。
測試週的具體要求
測試週的形式是實地試用，而非 bug 收集競賽。主辦方要求現有 Podman 用戶以平常使用的同一組容器及指令 —— 在安裝 conmon v3 的情況下 —— 執行，並與現行版本的結果作出比較。這類並排比較正是此類重寫所迫切需要的：效能回歸及行為差異往往相當微妙，最易被那些本身已十分熟悉自身工作負載的人發現。
對採用者的意義
是次重寫亦置於開源基建更廣泛的變遷之中。近年，語言團隊已將多個主要系統組件逐步移離 C，動機源於廣泛部署軟件反覆出現的記憶體安全漏洞。Rust 在該討論中屢次被提為答案，而 conmon 屬於較早期的例子，顯示此路線開始觸及容器 runtime 層，而非更為人所見的應用框架。
對於正在權衡是否採用 Rust 的機構而言，Podman 的決定提供了一個有用的參考點：重寫一個關鍵但體積不大的組件，在公開環境中測試，並邀請用戶去驗證，而非被動接受。
有興趣的參與者可於 Fedora Project 的 Test Days 頁面查閱報名詳情，並於 2026 年 10 月 12 至 18 日該週加入討論。