Open costateixeira opened 10 months ago
Hi @costateixeira, such Docker errors are classic connectivity issues that depend on your setup. In Docker networking, you use host.docker.internal
to point to the host that is running Docker. Given the URL I see, this expects this service in question to be bound on the host's port 9003 (either running directly on the host, separately from the Test Bed, or as part of the same Dockerised service but with a host port binding).
If the target service is not available on your host but is internal to the Dockerised service (and without a host port mapping), you should adapt it to match. For example if this is a fhir-service
container you would point to http://fhir-service:9003/fhir
). If I recall correctly from the PoC all such URLs are configurable via the UI as domain parameters (under Domain management).
By the way, I've had such questions come up loads of times in the past. If you like we can have a quick screenshare to fix it together.
After deploying it to a server, i get this when running the test. Do I need to change the test scripts or the docker compose?