You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It could be usefull sometimes not to map port to the host but use the container IP address directly to access the service exposed.
The problem I have is on my build & integration test server where several build can run at the same times resulting in conflict over the port mapped to the host. By not mapping port and using the container IP address directly would allow to have several instances of the same service available to the running jobs. Unfortunately I did not found a way using the docker-it-scala api to get a container IP address, only the mapped ports are available.
The text was updated successfully, but these errors were encountered:
jpthomasset
added a commit
to jpthomasset/docker-it-scala
that referenced
this issue
Oct 8, 2016
It could be usefull sometimes not to map port to the host but use the container IP address directly to access the service exposed.
The problem I have is on my build & integration test server where several build can run at the same times resulting in conflict over the port mapped to the host. By not mapping port and using the container IP address directly would allow to have several instances of the same service available to the running jobs. Unfortunately I did not found a way using the docker-it-scala api to get a container IP address, only the mapped ports are available.
The text was updated successfully, but these errors were encountered: