-
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
Add <return> to lines returned in podman-remote logs #6635
Conversation
Every line is sent back individually over the APIv2 as logs, but we are not adding the '\n' to give us line breaks. Signed-off-by: Daniel J Walsh <[email protected]>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rhatdan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Fixes #6539 |
Nice. Even handles the $ ./bin/podman-remote --url $MYSOCK run --name foo2 alpine sh -c "echo -n hi;echo hi2;echo bye"
hihi2
bye
$ ./bin/podman-remote --url $MYSOCK logs foo2
hihi2
bye ...even with |
@@ -370,7 +370,7 @@ func (ic *ContainerEngine) ContainerLogs(_ context.Context, nameOrIDs []string, | |||
case <-ctx.Done(): | |||
return err | |||
case line := <-outCh: | |||
_, _ = io.WriteString(options.Writer, line) | |||
_, _ = io.WriteString(options.Writer, line+"\n") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this do the right thing on Win-doze?
Podman logs streaming output is AFAIK a flake, restarting |
LGTM |
/lgtm |
Every line is sent back individually over the APIv2 as
logs, but we are not adding the '\n' to give us line breaks.
Signed-off-by: Daniel J Walsh [email protected]