Return container IP when attached to a single named network

[leszko]

In many cases the container is attached to a single, named network of the "bridge" mode. In such scenarios, DockerContainer.ContainerIP() should resolve this IP and return it.

For example, imaging the following container definition.

testcontainers.ContainerRequest{
    // ...
    Networks:     []string{"some-network"},
}

Before this change, the function container.ContainerIP(ctx) returns an empty string. After this change, it returns the correct container IP.

[mdelapenya]

Thanks for your contribution, also updating the tests! At first look, LGTM, will give it a try on CI before a final review.

[codecov]

Codecov Report

Merging #491 (1ebb44c) into main (d3af318) will increase coverage by 0.41%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #491      +/-   ##
==========================================
+ Coverage   69.65%   70.06%   +0.41%     
==========================================
  Files          21       21              
  Lines        2040     2048       +8     
==========================================
+ Hits         1421     1435      +14     
+ Misses        495      491       -4     
+ Partials      124      122       -2     

Impacted Files	Coverage Δ
docker.go	71.97% <100.00%> (+0.88%)	⬆️

Help us with your feedback. Take ten seconds to tell us how you rate us.

[leszko]

@mdelapenya If the PR is ok, can we get it merged into main?

[mdelapenya]

Merged, thanks for your contribution, much much appreciated!

[leszko]

Merged, thanks for your contribution, much much appreciated!

Thanks for merging :)

[mdelapenya]

My pleasure!!