Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: "wait for reaper 0743154e: no port to wait for" #2945

Open
srenatus opened this issue Jan 22, 2025 · 0 comments
Open

[Bug]: "wait for reaper 0743154e: no port to wait for" #2945

srenatus opened this issue Jan 22, 2025 · 0 comments
Labels
bug An issue with the library

Comments

@srenatus
Copy link
Contributor

srenatus commented Jan 22, 2025

Testcontainers version

0.35.0

Using the latest Testcontainers version?

Yes

Host OS

Linux

    OS Version: 22.04.5 LTS
    Kernel Version: 6.5.0-1025-azure
    Image Version: 20250105.1.0
    Systemd version: 249.11-0ubuntu3.12

Host arch

x86

Go version

1.23.5

Docker version

Docker Amazon ECR Credential Helper 0.9.0
Docker Compose v2 2.27.1
Docker-Buildx 0.19.3
Docker Client 26.1.3
Docker Server 26.1.3

Docker info

Github Runner :/

What happened?

Suddenly, a new type of failure spuriously hits our CI runs:

    e2e_test.go:46: generic container: create container: reaper: from container "0743154e": wait for reaper 0743154e: no port to wait for

The code in question is a helper method to spin up minio:

func minioContainer(ctx context.Context, t *testing.T) (testcontainers.Container, string) {
	t.Helper()
	tc, err := tc_minio.Run(ctx, "minio/minio:latest", testcontainers.CustomizeRequestOption(func(r *testcontainers.GenericContainerRequest) error {
		r.ContainerRequest.Env["MINIO_ROOT_USER"] = minioRootUser
		r.ContainerRequest.Env["MINIO_ROOT_PASSWORD"] = minioRootPassword
		return nil
	}))
	if err != nil {
		t.Fatal(err)
	}
	cs, err := tc.ConnectionString(ctx)
	if err != nil {
		t.Fatal(err)
	}
	return tc, cs
}

where tc_minio is "github.com/testcontainers/testcontainers-go/modules/minio".

I've never seen this before bumping TC from 0.34.0 to 0.35.0 last week. This used to run smoothly for a long while.

Relevant log output

Additional information

I'm sorry there aren't better logs -- but the test run uses TC a lot and this is the only failure in it. So previous and subsequent calls to reaper must have succeeded.

@srenatus srenatus added the bug An issue with the library label Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug An issue with the library
Projects
None yet
Development

No branches or pull requests

1 participant