podman-remote run and podman-remote start --attach does not handle detaching with detach keys correctly #7979
Labels
Good First Issue
This issue would be a good issue for a first time contributor to undertake.
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
podman-remote run
andpodman-remote start --attach
does not handle detaching with the detach keys<ctrl-p><ctrl-q>
correctly.Steps to reproduce the issue:
For
podman-remote run
:Start the podman service
podman-remote run -it alpine sh
detach with
<ctrl-p><ctrl-q>
For
podman-remote start --attach
:Start the podman service
podman-remote create -it --name test alpine sh
podman-remote start --attach test
detach with
<ctrl-p><ctrl-q>
Describe the results you received:
The process does not exit.
Describe the results you expected:
The process should exit with exitcode 0.
Additional information you deem important (e.g. issue happens only occasionally):
With
podman-remote start --attach
the error happens only if the container is not already started.It also works fine with
podman-remote attach
If I hit enter after detaching I get this error:
ERRO[0003] failed to write input to service: write unix @->/run/user/1000/podman/podman.sock: write: broken pipe
So it looks like it does detach and closes the pipe but the process does not exit. It instead waits for the container to exit.
Output of
podman version
:The text was updated successfully, but these errors were encountered: