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
Testcontainers returns the wrong gateway address if a container is running "inside" another container and has a custom network assigned. The current implementations just looks for networks with the name bridge:
This is interesting. In this case, I would expect the same issue for testcontainers-java. Can you conceptionally share a reproducer for us? (.NET reproducer is also fine, we can port it)
@kiview@eddumelendez@mdelapenya Do we know why we have the limitation and only consider networks with the name bridge? I know bridge is default, but what do we return in case of someone assigns a custom network?
Testcontainers returns the wrong gateway address if a container is running "inside" another container and has a custom network assigned. The current implementations just looks for networks with the name
bridge
:testcontainers-dotnet/src/Testcontainers/Containers/TestcontainersContainer.cs
Line 391 in 446f002
Originally posted by @ricardofmfreitasMP in #679 (comment)
The text was updated successfully, but these errors were encountered: