-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Detaching from container doesn't print newline #7751
Comments
Interested in opening a PR to fix this? |
How do I build without
|
@mohd-akram I'll take a look at this. |
@mohd-akram I'm getting identical results in both Docker and Podman on both 2.0.6 and upstream. can you clarify what exactly you're seeing differently? |
It's described in the issue. What is the result you're getting? |
➜ ~ podman run -it fedora /bin/bash |
Try this:
|
@ParkerVR Any progress on this? |
@rhatdan I made two PRs for this - one that is strictly the Docker compatible style and another that is internally consistent and prints a newline on detaches, let me know what you think |
It is probably better we follow Docker. |
@rhatdan the non-docker edition got merged in. If you want the Docker style I can update that PR to undo the other change, otherwise I will continue with the current detach method and test on the other cases brought up |
Ok I am fine with this as long as users don't complain. Can we close this issue? |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Steps to reproduce the issue:
Run
podman run -it fedora /bin/bash
Press
ctrl-p
ctrl-q
to detachDescribe the results you received:
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
On Docker, the additional message is printed to stderr.
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?
No
Additional environment details (AWS, VirtualBox, physical, etc.):
Physical laptop.
The text was updated successfully, but these errors were encountered: