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
When using DEBUG="testcontainers*", DEBUG=testcontainers:containers, or DEBUG=testcontainers:compose we should see the output of containers started via Docker Compose.
Actual Behaviour
Compose build and higher-level logs are printed, but container logs are not. This is particularly annoying when trying to debug why a container is failing to start. The logs will indicate that the container failed to start, but won't print any logs from the container.
Testcontainer Logs
...
Steps to Reproduce
Create a docker compose setup with a container that fails to start
Start docker compose environment with DockerComposeEnvironment(composeFilePath, fileName).up();
Observe the lack of container logs
Environment Information
Operating System: Linux
Docker Version: 24.0.7
Node version: 16
Testcontainers version: 10.2.1
The text was updated successfully, but these errors were encountered:
Expected Behaviour
When using
DEBUG="testcontainers*"
,DEBUG=testcontainers:containers
, orDEBUG=testcontainers:compose
we should see the output of containers started via Docker Compose.Actual Behaviour
Compose build and higher-level logs are printed, but container logs are not. This is particularly annoying when trying to debug why a container is failing to start. The logs will indicate that the container failed to start, but won't print any logs from the container.
Testcontainer Logs
...
Steps to Reproduce
DockerComposeEnvironment(composeFilePath, fileName).up();
Environment Information
The text was updated successfully, but these errors were encountered: