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.
podman --remote exec ignores empty detach keys · containers/podman#28193 | Good First Issue