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

No carriage returns when working interactively inside a container #1678

Closed
leonboot opened this issue Jun 2, 2017 · 3 comments
Closed

No carriage returns when working interactively inside a container #1678

leonboot opened this issue Jun 2, 2017 · 3 comments

Comments

@leonboot
Copy link

leonboot commented Jun 2, 2017

Expected behavior

When running an interactive shell inside a container, a carriage return should be done after each newline. So ls -1 should produce something like:

file1
file2
file3
...

Actual behavior

Line breaks get a newline, but no carriage return. The command ls -1 produces:

file1
     file2
          file3

Information

  • Edge version 17.06.0-rc1-ce-mac13 (18169)
  • Diagnostic ID: 1A51357B-1DE7-4A23-A1B4-2D251FA7D0C8

Steps to reproduce the behavior

  1. Make sure you're on Edge version 17.06.0-rc1-ce-mac13 (18169)
  2. Spin up an interactive shell in a docker container: docker run --rm -it alpine:latest sh
  3. run ls -1 / in the container
  4. Note that each new line starts on a new line, but at the colum the last line ended.
@amancevice
Copy link

This looks like a dup of #1671 and #1672

@leonboot
Copy link
Author

leonboot commented Jun 2, 2017

@amancevice you're absolutely right. Guess I should rub that sand out of my eyes before reporting an issue. I'll close it.

@leonboot leonboot closed this as completed Jun 2, 2017
@docker-robott
Copy link
Collaborator

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked

@docker docker locked and limited conversation to collaborators Jun 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants