-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ctrl+C doesn't kill the container using podman run -i
with podman machine
#14707
Comments
Can you try adding |
|
oh... that was with
|
Looking further, I don't see a sig-proxy implementation for remote Podman. Should not be difficult to add. |
@mheon can you assign this to me? |
Done |
A friendly reminder that this issue had no activity for 30 days. |
@boaz0 any movement on this? |
A friendly reminder that this issue had no activity for 30 days. |
This is actively being worked on by @boaz0 |
When should we expect a release? |
Week after next, probably
…On Thu, Sep 22, 2022 at 16:30 Alexander Ponimaskin ***@***.***> wrote:
When should we expect a release?
—
Reply to this email directly, view it on GitHub
<#14707 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB3AOCEKK7SINVT3F3S5JWDV7S6UZANCNFSM5ZS6FUOA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Same issue here, |
Please don't add to closed issue. Open a new issue, but first make sure the app within the container responds to ctr-c. |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
It's impossible to stop container attached to the terminal (flags
-a
,-i
or-t
) by pressing Ctrl+C.Steps to reproduce the issue:
podmain machine start
podman run -i nginx
press
ctrl+c
podman ps --noheading
Describe the results you received:
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
Created
andStatus
indocker ps
output are suspicious. They say14 hours
despite the fact that container is several seconds old.Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)
Yes/
NoAdditional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: