Skip to content
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

podman-remote run and podman-remote start --attach does not handle detaching with detach keys correctly #7979

Closed
Luap99 opened this issue Oct 9, 2020 · 1 comment
Assignees
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.

Comments

@Luap99
Copy link
Member

Luap99 commented Oct 9, 2020

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind bug

Description

podman-remote run and podman-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:

  1. Start the podman service

  2. podman-remote run -it alpine sh

  3. detach with <ctrl-p><ctrl-q>

For podman-remote start --attach:

  1. Start the podman service

  2. podman-remote create -it --name test alpine sh

  3. podman-remote start --attach test

  4. 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:

$ podman-remote version
Client:
Version:      2.2.0-dev
API Version:  2.0.0
Go Version:   go1.14.9
Git Commit:   71d675a164ee64111db1a9214673a3498b3aa123
Built:        Fri Oct  9 13:10:16 2020
OS/Arch:      linux/amd64

Server:
Version:      2.2.0-dev
API Version:  2.0.0
Go Version:   go1.14.9
Git Commit:   71d675a164ee64111db1a9214673a3498b3aa123
Built:        Fri Oct  9 13:10:05 2020
OS/Arch:      linux/amd64
@openshift-ci-robot openshift-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Oct 9, 2020
@rhatdan rhatdan added the Good First Issue This issue would be a good issue for a first time contributor to undertake. label Oct 9, 2020
@andylibrian
Copy link
Contributor

Let me look into this

/assign

andylibrian added a commit to andylibrian/podman that referenced this issue Oct 16, 2020
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 22, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
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.
Projects
None yet
Development

No branches or pull requests

4 participants