-
Notifications
You must be signed in to change notification settings - Fork 64
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 STDOUT/STDERR #4
Comments
Thank you for the feedback, i'll look into it. |
Check my latest commit. Now the podman log should be forwarded into the nomad logging facility. It's thus also visible in the nomad web ui and of course accessible via nomad alloc logs. Again there is a small unit test and a hint in the readme. |
This is much better now and I can see STDOUT in Nomad log. Thanks. However STDERR is not quite working as expected. Consider the following example:
Nomad show output of both commands in Logs/stdout while Logs/stderr is empty. The command line reproducer would be something like
The above command also prints the output of both commands to STDOUT because Podman apparently redirects STDERR-->STDOUT when option The following command (without
Therefore I suspect that driver starts Podman with equivalent of |
Thank you for the hints, i will give it another try. |
@onlyjob I'm a bit unsure about the "right" approach, so i filed a question into podmans issue tracker. |
@towe75 I think there is mention of this in #37 but we currently don't have STDERR logging, we ultimately will likely need something like docker logger to stream logs from containers to alloc fifos |
STDOUT
andSTDERR
are not visible in Nomad.Something like the following config demonstrates that the output is going nowhere and no log appears in the alloc directory:
The text was updated successfully, but these errors were encountered: