[Bug]: Starting with 1.20.2 we can no longer get the logs of a container that failed to start

Module

Core

Testcontainers version

1.20.2+

Using the latest Testcontainers version?

Yes

Host OS

Macos

Host Arch

ARM

Docker version

Client:
 Version:           27.5.1
 API version:       1.47
 Go version:        go1.22.11
 Git commit:        9f9e405
 Built:             Wed Jan 22 13:37:19 2025
 OS/Arch:           darwin/arm64
 Context:           desktop-linux

Server: Docker Desktop 4.38.0 (181591)
 Engine:
  Version:          27.5.1
  API version:      1.47 (minimum version 1.24)
  Go version:       go1.22.11
  Git commit:       4c9b3b0
  Built:            Wed Jan 22 13:41:25 2025
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Version:          1.7.25
  GitCommit:        bcc810d6b9066471b0b6fa75f557a15a1cbf31bb
 runc:
  Version:          1.1.12
  GitCommit:        v1.1.12-0-g51d5e946
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

What happened?

Starting with 1.20.2 we can no longer get the log output of a container that failed to start. The stop method is called automatically, and that clears the containerId.

Relevant log output

Additional Information

No response

Start in core/src/main/java/org/testcontainers/containers/GenericContainer.java at the stop method linked in the issue, and trace how containerId is cleared after a failed start. Check the Core container lifecycle tests for the relevant startup-failure path. Done means logs remain retrievable after a container fails to start, with a regression test covering that behavior.