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
I think (...) that the first time you run a docker exposing that port, it actually uses the port you request - but then the port is not available for the next time you run a docker exposing that port, so it automatically maps to a different one.
I.e., it is docker not the jig doing that, as far as I understand.
Yeah, by default Docker uses a random port on the host side so that containers that require the same port don't collide (i.e., we could both run a MySQL container on a server without colliding with each other).
We can add in some explicit port mappings within the jig (after the workshop, currently have no bandwidth) that are passed through to Docker.
Hence its difficult to document which ports a user should connect to.
![image](https://user-images.githubusercontent.com/620938/60343501-08a58280-99ac-11e9-820d-db1c662114ad.png)
See for example this from Terrier:
The jig could simply assume that it should expose the ports as they were requested.
The text was updated successfully, but these errors were encountered: