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
Somewhere between versions v0.27.0 and v0.32.0 this library stopped printing out container logs whenever container failed and now I just have "failed to start container: container exited with code 1" in output. Please return previous behavior that helped troubleshooting.
Relevant log output
failed to start container: container exited with code 1
Additional information
No response
The text was updated successfully, but these errors were encountered:
Hi @strowk could you provide an code snippet or a reproduction repo for this? The error message you mentioned happens in the checkState function, that happens inside the wait strategies. So it seems something is causing the containers not to reach the desired state, but instead being in the "exited" one:
funccheckState(state*types.ContainerState) error {
switch {
casestate.Running:
returnnilcasestate.OOMKilled:
returnerrors.New("container crashed with out-of-memory (OOMKilled)")
casestate.Status=="exited":
returnfmt.Errorf("container exited with code %d", state.ExitCode)
default:
returnfmt.Errorf("unexpected container status %q", state.Status)
}
}
Also it's interesting that the failed to start container log entry appears in our codebase for the testable examples in the modules, that's why I'm very interested in seeing your repro code to be able to debug it and find the root cause for this issue.
Testcontainers version
0.32.0
Using the latest Testcontainers version?
No
Host OS
Linux
Host arch
ARM
Go version
1.22.4
Docker version
Docker info
What happened?
Somewhere between versions v0.27.0 and v0.32.0 this library stopped printing out container logs whenever container failed and now I just have "failed to start container: container exited with code 1" in output. Please return previous behavior that helped troubleshooting.
Relevant log output
Additional information
No response
The text was updated successfully, but these errors were encountered: