Devservices and host exposed ports #40573
scrocquesel
started this conversation in
Design Discussions
Replies: 1 comment 6 replies
-
Good question - I can see the need and I agree it would be nice to have an API for this or at least a decent convention. Just have to be careful we don't end up accidentally expose too much local access (i.e. for remote hosts) and I'm curious if this just works in windows/mac where there is an extra level of indirection of the network (at least when using podman) |
Beta Was this translation helpful? Give feedback.
6 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've seen some use cases where test containers need to connect back to the host application:
Typically, the approach involves configuring test containers to allow access to the host and then let the user manually add host ports with
Testcontainers.exposeHostPorts
. However, this method has its drawbacks:quarkus.http.port
value and find the right way to call the method at the right moment.Would it be possible to have a better and seamless integration of this use case in Dev Services ?
Beta Was this translation helpful? Give feedback.
All reactions