ar-sematell
commented
1 month ago Same issue, solved with:
// HOTFIX: testcontainers-go v0.32.0
// https://github.com/testcontainers/testcontainers-go/issues/2670
type hotfix2670 struct{}
func (h hotfix2670) Customize(req *testcontainers.GenericContainerRequest) error {
originalHook := req.LifecycleHooks[0].PostStarts[0]
req.LifecycleHooks[0].PostStarts[0] = func(ctx context.Context, container testcontainers.Container) error {
var err error
for retry := 0; retry < 10; retry++ {
err = originalHook(ctx, container)
if err == nil {
break
}
time.Sleep(time.Second)
}
return err
}
return nil
}
func setupKafka(t *testing.T, ctx context.Context) *kafka.KafkaContainer {
t.Helper()
testcontainers.Logger = log.New(io.Discard, "", 0)
kafkaContainer, err := kafka.Run(ctx, "confluentinc/confluent-local:7.5.0",
kafka.WithClusterID("test-cluster"),
hotfix2670{},
)
require.NoError(t, err)
t.Cleanup(func() { require.NoError(t, kafkaContainer.Terminate(ctx)) })
return kafkaContainer
}
aakso
stevenh
mdelapenya
tigerquoll
Testcontainers version
0.32.0
Using the latest Testcontainers version?
Yes
Host OS
MacOS
Host arch
ARM
Go version
1.21.12
Docker version
Docker info
What happened?
related to #2543
Unfortunately, the "port not found" error still seems to be present with v0.32.0.
I see it mainly with the Kafka module but also occasionally with
testcontainers.GenericContainertoo.The code snippet I'm using the start the Kafka test container:
So pretty standard.
Relevant log output
Additional information
I'm able to mitigate the error for Kafka module by wrapping the
PostStartslifecycle hooks and retrying on error. In my case it's the first hook that always fails. It seems to fail toc.MappedPortcall. So far, a single retry has been enough to mitigate the problem.