When using exasol-test-setup-abstraction-server in integration tests where we need to access the Exasol database from another docker container, the connection info object returns exasolContainer.getHost() as host which usually is localhost. This name however won't work when trying to access Exasol from another docker container. In this case the exasolContainer.getHostIp() might be more helpful.
AC
The SqlConnectionInfo object returned by getConnectionInfo() contains additionally the result of exasolContainer.getHostIp() in case of ExasolTestcontainerTestSetup.
For StandaloneExasolTestSetup we need to find another value that makes sense in this case.
When using exasol-test-setup-abstraction-server in integration tests where we need to access the Exasol database from another docker container, the connection info object returns
exasolContainer.getHost()
as host which usually islocalhost
. This name however won't work when trying to access Exasol from another docker container. In this case theexasolContainer.getHostIp()
might be more helpful.AC
SqlConnectionInfo
object returned bygetConnectionInfo()
contains additionally the result ofexasolContainer.getHostIp()
in case ofExasolTestcontainerTestSetup
.StandaloneExasolTestSetup
we need to find another value that makes sense in this case.Workaround
Use hard-coded IP address
172.17.0.1
.