Use fixed ports in Dev Service for Keycloak on shared network & user request

[michalvavrik]

fixes: #27763

When Docker host name isn't localhost/127.0.0.1, it's likely that exposed host port don't equal exposed container port. TestContainers are exposing random host port, fixed port is only exposed from the container's perspective. That's a good thing. There are only 2 situations we actually need fixed ports:

• user configured fixed port (user knows what he is doing)
• shared network for docker internal communication

I replaced usage of random fixed port for sharedContainer with useSharedNetwork as fixed port has no relation to sharedContainer at all, I think it was a typo at first place introduced here #21999. Second thing I did is to use auto-detected host name and port for external calls only (test runner -> docker, e.g. when Dev Services for Keycloak are creating realm, users and KeycloakTestClient is used inside tests). For internal communication (within shared network), random fixed port is still used as it's okay.

As for tests, to my knowledge you can only test this when Docker endpoint isn't listening on localhost (e.g. remote Docker daemons). I run current test coverage related to Dev Services for Keycloak with local Docker engine and TestContainers Cloud (to verify host name != localhost scenarios). If you have suggestions on how this can be covered with IT, I'm happy to learn.

cc @geoand @sberyozkin

[quarkus-bot]

Failing Jobs - Building 04582da

Status	Name	Step	Failures	Logs	Raw logs
✔️	JVM Tests - JDK 11
✔️	JVM Tests - JDK 17
✖	JVM Tests - JDK 17 MacOS M1	Set up runner	⚠️ Check →	Logs	Raw logs
✔️	JVM Tests - JDK 18

[sberyozkin]

@michalvavrik Nice analysis, LGTM, but lets wait for Georgios to review/approve

[wjglerum]

Awesome work @michalvavrik! Thanks for this fix. I just managed to verify this locally and also works for me 👍

[michalvavrik]

thank you for confirmation @wjglerum :-)