Ctrl+C doesn't kill the container using podman attach
with podman machine
#16662
Labels
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.
macos
MacOS (OSX) related
remote
Problem is in podman-remote
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Cannot stop container attached by
podman attach
by pressing Ctrl+CSimilar to #14707 but for
podman attach
commandSteps to reproduce the issue:
podman machine start
podman run --rm -d --name test nginx
podman attach test
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):
It works as expected if
2.
and3.
are replaced bypodman run --rm -it nginx
.Output of
podman version
:Output of
podman info
:Package info (e.g. output of
rpm -q podman
orapt list podman
orbrew info podman
):brew info podman ==> podman: stable 4.3.1 (bottled), HEAD Tool for managing OCI containers and pods https://podman.io/ /opt/homebrew/Cellar/podman/4.3.1 (185 files, 47.6MB) * Poured from bottle on 2022-11-29 at 12:47:46 From: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/podman.rb License: Apache-2.0 and GPL-3.0-or-later ==> Dependencies Build: go-md2man ✘, go@1.18 ✘ Required: qemu ✔ ==> Options --HEAD Install HEAD version ==> Caveats zsh completions have been installed to: /opt/homebrew/share/zsh/site-functions To restart podman after an upgrade: brew services restart podman Or, if you don't want/need a background service you can just run: /opt/homebrew/opt/podman/bin/podman system service --time=0 ==> Analytics install: 29,640 (30 days), 79,815 (90 days), 238,131 (365 days) install-on-request: 27,177 (30 days), 75,512 (90 days), 232,844 (365 days) build-error: 24 (30 days)
Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
macOS Ventura 13.0.1
The text was updated successfully, but these errors were encountered: