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
container output becomes windows-ised #30156
Comments
The default terminal setting for a new pty on linux(unix98) has +ONLCR, on containerd-shim we create a net pty, resulting in Should we make a PR like opencontainers/runc@eea28f4? |
Reopening this, because the version of containerd that's used has not been bumped yet; |
@mlaventure can containerd be bumped, or should that go in sync with RunC? |
|
opened #30226 to bump containerd version |
Thinking about this more, I think we should probably revert that change from The issue is actually more complex than I first thought:
Note that the logs created by the daemon will also record the output of a raw terminal (which is the expected behavior AFAIC). So really the solution for the client side would be to have it filter all the terminal escape characters when it is receiving a terminal output but is not outputing to one. However, I'm not sure it is worth the effort. |
/cc @crosbymichael maybe you have a different POV on this. |
Also see the discussion on #8513 (comment). Is |
@mlaventure If the receiver is not a terminal, then it should not use The case in this issue:
I think it's invalid because the
or:
If you want to print the output out of docker client (some terminal that hasn't been setup to raw mode), you just shouldn't use
Which also works well. |
Description
If we running a container with a tty(-t/--tty), the output gets a
\n
translated to\r\n
on output.This happens for bothdocker run
anddocker exec
.Steps to reproduce the issue:
-t/-tty
Describe the results you received:
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
Output of
docker version
:Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: