From 549e7a0262fa47bd08f814e1764533b40fcf24e0 Mon Sep 17 00:00:00 2001 From: heitbaum Date: Thu, 6 Jan 2022 16:19:20 +1100 Subject: [PATCH] tools/docker/README.md: log-driver command line update update the `docker run` command to set `--log-driver none` otherwise the logs go through to journald observed the journald logs during the testing of systemd v250 --- tools/docker/README.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/tools/docker/README.md b/tools/docker/README.md index cfbfd8e8c9..dd1dbe99fc 100644 --- a/tools/docker/README.md +++ b/tools/docker/README.md @@ -33,13 +33,18 @@ Change to your LibreELEC.tv development directory that you checked out with
Then use the following command to build LibreELEC images inside a new container based on the docker image tagged with `libreelec`. (The `pwd` uses the current directory - which must have the LibeELEC `Makefile` in it.) ``` -docker run --rm -v `pwd`:/build -w /build -it libreelec make image +docker run --rm --log-driver none -v `pwd`:/build -w /build -it libreelec make image ``` Use `--env`, `-e` or `--env-file` to pass environment variables used by the LibreELEC buildsystem. ``` -docker run --rm -v `pwd`:/build -w /build -it -e PROJECT=RPi -e DEVICE=RPi4 -e ARCH=arm libreelec make image +docker run --rm --log-driver none -v `pwd`:/build -w /build -it -e PROJECT=RPi -e DEVICE=RPi4 -e ARCH=arm libreelec make image ``` See https://docs.docker.com/engine/reference/commandline/run/ for details on `docker run` usage. + +Note: `dockerd` is set to send all its logs to journald using the setting `--log-driver=journald` (so if you don't set the `--log-driver none` for your `docker run` these logs will be sent through to your log. +Refer: + +https://github.com/LibreELEC/LibreELEC.tv/blob/140ad28a258167e0e87daf1e474db37215b2caf3/packages/addons/service/docker/source/system.d/service.system.docker.service#L12