We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When querying logs for containers with a tty, the logs stream is not multiplexed via headers but just returns the raw output: https://github.com/docker/cli/blob/86e1f04b5f115fb0b4bbd51e0e4a68233072d24b/vendor/github.com/docker/docker/client/container_logs.go#L19 The current logs implementation will parse random STDOUT data as a length header and then tries to perform a read_exact with usually an unreasonably large length which runs into EOF error. The observed behavior is that logs immediately exits without returning any output.
read_exact
logs
The text was updated successfully, but these errors were encountered:
Identical issue encountered by docker-py: docker/docker-py#630
Sorry, something went wrong.
No branches or pull requests
When querying logs for containers with a tty, the logs stream is not multiplexed via headers but just returns the raw output: https://github.com/docker/cli/blob/86e1f04b5f115fb0b4bbd51e0e4a68233072d24b/vendor/github.com/docker/docker/client/container_logs.go#L19
The current logs implementation will parse random STDOUT data as a length header and then tries to perform a
read_exact
with usually an unreasonably large length which runs into EOF error. The observed behavior is thatlogs
immediately exits without returning any output.The text was updated successfully, but these errors were encountered: