containers/podman

podman --remote exec ignores empty detach keys

Open

#28,193 建立於 2026年3月4日

在 GitHub 查看
 (6 留言) (0 反應) (1 負責人)Go (31,686 star) (3,107 fork)batch import
Good First Issuekind/bugstale-issuetriaged

描述

I've confirmed the fix in 5.8.0 for https://github.com/containers/podman/issues/27414 but it only fixes the issue for podman run, not podman exec. In the latter case, an empty string is treated as nothing and the default "C-p,C-q" is used instead of disabling the detach sequence.

貢獻者指南

技術棧
go
領域
clibackend
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
active
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Go programmingFamiliarity with Podman CLIUnderstanding of detach keys
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
60
研究方向
The previous fix for podman run (#27414) handled empty detach keys by disabling detach. For podman exec, the same logic needs to be applied. Likely in the exec implementation around libpod/options or cmd/podman/exec. Check where the detach keys are parsed and ensure that an empty string results in no detach sequence. Review linked PR for the run fix to replicate the approach.