-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Docker CLI display poor output based on command docker image history --no-trunc <image_name>
from Power Shell.
#3329
Comments
Thanks for reporting; I think the cause for this is that the history output can be very wide (depending on what's in the history), which causes the shell to wrap the output. I don't think there's a way to make the shell output wider than the shell itself is, other than truncating the output (but this wouldn't allow you to view each line (i.e., not allow you to horizontally scroll)). Not sure if PowerShell is handling this different, but in a Bash terminal, I'm able to copy the output, and pasting it in an editor, I get the lines without wrapping; e.g.:
I can also pipe the output to
You may be able to redirect the output to a file (not exactly sure what the right syntax for that is on PowerShell) |
Description
I am going to check image history in full by issue command:
docker image history --no-trunc <image_name>
But the output of this command is very hard to read.
I have to scroll down lines to read info comming next.
Here is how it looks:
Is there any solution to this problem?
Steps to reproduce the issue:
docker image history --no-trunc <any_image_name_available>
Describe the results you received:
Text ouput in poor format and hard to read.
Describe the results you expected:
I expect to read the --no-trunc version in less like how
journalctl
works on Ubuntu.Additional information you deem important (e.g. issue happens only occasionally):
Output of
docker version
:Output of
docker info
:The text was updated successfully, but these errors were encountered: