Artemis Dev Service does not work with IT running as container

[vsevel]

Here is the reproducer and instructions:
https://github.com/TechAndOperations/quarkus_reproducers/tree/issue_artemis_devservice_jib_network

the build fails if executing:

mvn clean verify -DskipITs=false -Dquarkus.container-image.build=true 

it works with:

mvn clean verify -DskipITs=false -Dquarkus.container-image.build=false

this is related to the connection parameters passed to the IT JVM:

2026-03-03 19:36:12,708 INFO  [io.quarkus.test.common.DefaultDockerContainerLauncher] (main) Executing "docker run --name quarkus-integration-test-hRqOG -i --rm -p 8081:8081 -p 8444:8444 --net=2a0eecdbfa1f410f6a286d53a89a55a70cf4b0ddd4d3b09c648b8b87db02f67a --env QUARKUS_LOG_CATEGORY__IO_QUARKUS__LEVEL=INFO --env QUARKUS_HTTP_PORT=8081 --env QUARKUS_HTTP_SSL_PORT=8444 --env TEST_URL=http://localhost:${quarkus.http.test-port:8081} --env QUARKUS_PROFILE=prod --env QUARKUS_CONTAINER_IMAGE_BUILD=true --env QUARKUS_TEST_CONTAINER_NETWORK=2a0eecdbfa1f410f6a286d53a89a55a70cf4b0ddd4d3b09c648b8b87db02f67a --env QUARKUS_IRONJACAMAR_RA_CONFIG_CONNECTION_PARAMETERS=host=localhost;port=50176;protocols=CORE sevel/quarkus-jib-jms:1.0.0-SNAPSHOT"

we should connect to artemis using the docker host, or the shared network, but not localhost

cc @holly-cummins @ozangunalp

[turing85]

@vsevel is this an issue only with quarkus-artemis-jms-ra? Or does this issue also occur with quarkus-artemis-jms or quarkus-artemis-core?

[vsevel]

is this an issue only with quarkus-artemis-jms-ra?

I suspect it affects also the non ra dev service. but I have not tested, as I do not work with it.
so far I have seen issues on those other dev services: quarkiverse/quarkus-vault#481 and quarkusio/quarkus#52809
it is not clear to me at this point if this is just a coincidence, or a similar problem. yet, it sounds there is a common networking theme between those different issues.

[turing85]

I can confirm that this bug also hits quarkus-artemis-jms and quarkus-artemis-core.

[turing85]

This should be resolved by quarkusio/quarkus#53016. We will leave the issue open and check when the fix is released.