Skip to content

Commit

Permalink
clarify test logging
Browse files Browse the repository at this point in the history
  • Loading branch information
JoshMcCullough authored Oct 13, 2023
1 parent 0b8e193 commit 05a3798
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -231,7 +231,7 @@ The tests use a customized NGINX image, distinct from the main image, as well as

After making changes and finding that some tests fail, it can be difficult to understand why. By default, logs are written to Docker's internal log mechanism, but they won't be persisted after the test run completes and the containers are removed.

In order to persist logs, you can configure the log driver to use. You can do this by setting the environment variable `LOG_DRIVER` before running the tests. On Linux/Unix systems, you can use the driver `journald`, as follows:
If you'd like to persist logs across test runs, you can configure the log driver to use `journald` (on Linux/Unix systems for example). You can do this by setting the environment variable `LOG_DRIVER` before running the tests:

```shell
# need to rebuild the test runner with the proper log driver
Expand Down

0 comments on commit 05a3798

Please sign in to comment.