containers/podman

podman --remote exec ignores empty detach keys

Open

#28193 opened on Mar 4, 2026

View on GitHub
 (6 comments) (0 reactions) (1 assignee)Go (31,686 stars) (3,107 forks)batch import
Good First Issuekind/bugstale-issuetriaged

Description

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.

Contributor guide

Tech stack
go
Domain
clibackend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Go programmingFamiliarity with Podman CLIUnderstanding of detach keys
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
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.