-
Notifications
You must be signed in to change notification settings - Fork 309
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
Only log to stderr if --log
is not provided
#1547
Conversation
@giuseppe let me know if you still prefer the |
Ephemeral COPR build failed. @containers/packit-build please check. |
podman system tests failed. @containers/packit-build please check. |
9d3551f
to
a5e3f04
Compare
Ephemeral COPR build failed. @containers/packit-build please check. |
podman system tests failed. @containers/packit-build please check. |
--log
is not provided--log
is not provided
In any other case we log to the dedicated log driver for consistency reason. This avoids having another option like `--log-stderr`. Signed-off-by: Sascha Grunert <[email protected]>
a5e3f04
to
a295e70
Compare
Ephemeral COPR build failed. @containers/packit-build please check. |
--log
is not provided--log
is not provided
@giuseppe PTAL, we still have to report errors to the CLI to make containerd integration tests happy. |
podman system tests failed. @containers/packit-build please check. |
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.
LGTM
thanks for working on this alternative. I am fine with it (and containerd too 😄 ) |
In any other case we log to the dedicated log driver for consistency reason. This avoids having another option like
--log-stderr
.Needs #1545
Alternative to #1542