support IT with jib

[vsevel]

see this reproducer:
https://github.com/TechAndOperations/quarkus_reproducers/tree/issue_vault_devservice_jib

when executing mvn clean verify -DskipITs=false -Dquarkus.container-image.build=true , this fails with:

2026-02-27 16:58:28,789 INFO  [org.testcontainers.containers.wait.strategy.HttpWaitStrategy] (ForkJoinPool.commonPool-worker-1) /ecstatic_johnson: Waiting for 60 seconds for URL: http://vault-l3q8f:56517/v1/sys/health (where port 56517 maps to container port 8200)
2026-02-27 16:59:28,802 ERROR [tc.hashicorp/vault:1.15.2] (ForkJoinPool.commonPool-worker-1) Could not start container: org.testcontainers.containers.ContainerLaunchException: Timed out waiting for URL to be accessible (http://vault-l3q8f:56517/v1/sys/health should return HTTP [200])
        at org.testcontainers.containers.wait.strategy.HttpWaitStrategy.waitUntilReady(HttpWaitStrategy.java:320)
...

whereas the vault seems to be started successfully:

==> Vault server started! Log data will stream in below:

if executing mvn clean verify -DskipITs=false -Dquarkus.container-image.build=false, then everything works as expected

[vsevel]

could you give me your input @ozangunalp @holly-cummins ?
I adapted the dev service to the new api recently, using redis as an example
I am not sure the dev service has never been tested with jib.
when we use quarkus.container-image.build=true, I can see that we are waiting on http://vault-dcbxe:55326
whereas when quarkus.container-image.build=false, we search for http://localhost:59896, which works.
the process that starts the dev service is not running in a container, so I do not know how it could know vault-dcbxe
is there anything wrong in the way the vault dev service is designed?