You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a way to get the docker logs command to behave as expected when using docker logs with other containers?
Specifically, I'm trying to run Kodi, which currently doesn't output anything to stdout, meaning running docker logs will result in no logs. I'm trying to address this by forcing the output of Kodi's real logs into /dev/stdout (see below). This causes the logs to come up when running the x11docker command, but not when running docker logs. In general Docker picks up all output to stdout and stderr and outputs that when running docker logs.
The code snippet is as follows. This is run just before running Kodi in the entry-point.sh.
I can confirm that docker logs gives no output. x11docker does a lot of redirection to grab container output, so docker logs does not get it.
I'll have a look how to improve this.
I did some changes that allow docker logs to show the container output.
The changes need some further tests, e.g. on MS Windows, but basically it should work.
Please try out and report issues if something comes up.
Is there a way to get the
docker logs
command to behave as expected when usingdocker logs
with other containers?Specifically, I'm trying to run Kodi, which currently doesn't output anything to stdout, meaning running
docker logs
will result in no logs. I'm trying to address this by forcing the output of Kodi's real logs into/dev/stdout
(see below). This causes the logs to come up when running thex11docker
command, but not when runningdocker logs
. In general Docker picks up all output tostdout
andstderr
and outputs that when runningdocker logs
.The code snippet is as follows. This is run just before running Kodi in the
entry-point.sh
.The text was updated successfully, but these errors were encountered: