[Bug]: Two custom containers can't connect on docker using testcontainers #8733
dbraun1991
started this conversation in
General
Replies: 1 comment 2 replies
-
Hi, few notes:
Looking at the code again, you probably don't want to mark |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Module
Core
Testcontainers version
1.19.8
Using the latest Testcontainers version?
Yes
Host OS
MacOS
Host Arch
ARM
Docker version
Client: Cloud integration: v1.0.35+desktop.13 Version: 26.1.1 API version: 1.45 Go version: go1.21.9 Git commit: 4cf5afa Built: Tue Apr 30 11:44:56 2024 OS/Arch: darwin/arm64 Context: desktop-linux Server: Docker Desktop 4.30.0 (149282) Engine: Version: 26.1.1 API version: 1.45 (minimum version 1.24) Go version: go1.21.9 Git commit: ac2de55 Built: Tue Apr 30 11:48:04 2024 OS/Arch: linux/arm64 Experimental: false containerd: Version: 1.6.31 GitCommit: e377cd56a71523140ca6ae87e30244719194a521 runc: Version: 1.1.12 GitCommit: v1.1.12-0-g51d5e94 docker-init: Version: 0.19.0 GitCommit: de40ad0
What happened?
=== First ===
Java code from the testcontainers library behaves differently.
=== Second ===
The bookingEndpoint gets an IP that is not sufficient for connecting.
Neither of the following ...
... leads to a connection.
Needed solution for:
bookingEndpoint.withEnv("AUTH_URL", authEndpointBaseURL);
=== Third ===
Executing the JARs without Testcontainers locally -> works as a charm, just as in gitlab pipeline
Relevant log output
Custom Log Output:
Additional Information
https://stackoverflow.com/questions/78352477/testcontainers-container-gethost-is-behaving-differently-locally-vs-gitlab-pi
Beta Was this translation helpful? Give feedback.
All reactions