[Feature request]: set fixed port for ryuk container

[tomair37]

Why ?

I'm currently working on a windows 7 company computer. We use Vagrant to set fixed port between the host and the unix virtual machine whith Docker. Actually the port used by the Ryuk container is dynamic, it will be more convenient if we can set the port manually.

Proposed solution

When I instanciate a Generic Container, I cannot acces the Ryuk container port. Would it be ok, if I make a pull request to add a property file (testcontainer.properties), with a property to set the port.
Or maybe have you got any more convinient way to achieve this goal.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe this is a mistake, please reply to this comment to keep it open. If there isn't one already, a PR to fix or at least reproduce the problem in a test case will always help us get back on track to tackle this.

[stale]

This issue has been automatically closed due to inactivity. We apologise if this is still an active problem for you, and would ask you to re-open the issue if this is the case.

[jtama]

This would still be usefull in secure envs, where expose ports are limited...

[shailjadon]

Random ports are difficult to manage especially if you are using remote docker host EC2 machines where we need to open the specific TCP ports which becomes extremely difficult since ports keep on changing.

[bsideup]

Testcontainers randomizes all ports, not only Ryuk's ones. I am afraid you will need to find some other way of managing this (eg establishing a tunnel between your machine and the EC2 instance)