Add container logs in case testcontainer exited unexpectedly #1895
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When running tests against the
nginxproxy/nginx-proxy:test
it can happen that someone uses an invalid configuration yaml file for spinning up containers. It then can happen that the proxy container exits immediately and the test logs don't provide any further information.This PR adds the docker container logs output in case the
nginxproxy/nginx-proxy:test
exited unexpectedly before tests are run.A sample output looks like this:
The additional warning helps to figure out what went wrong especially when running test on CI platforms like Github Actions.