-
Notifications
You must be signed in to change notification settings - Fork 362
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple port in hostConfig.portBindings doesn't work #890
Comments
@rocks4530 your example should work. Can you create a minimal repo/example which demonstrates the issue? |
HI @orzeh , docker ps commands shows this CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES |
@rocks4530 ok, I can reproduce it with your example. I need some time to dig into this. |
@orzeh thanks. |
@rocks4530 actually it's working, please try to access these ports. Because of Docker API awkwardness, exposed ports are not being displayed neither in CLI nor in API responses, see also this issue. |
good to know that. And thanks. Will try out to see. |
To read: * https://danwalsh.livejournal.com/74095.html * bmuschko/gradle-docker-plugin#890 Maybe it's because of multiple port exports?
To read: * https://danwalsh.livejournal.com/74095.html * bmuschko/gradle-docker-plugin#890 Maybe it's because of multiple port exports?
To read: * https://danwalsh.livejournal.com/74095.html * bmuschko/gradle-docker-plugin#890 Maybe it's because of multiple port exports?
To read: * https://danwalsh.livejournal.com/74095.html * bmuschko/gradle-docker-plugin#890 Maybe it's because of multiple port exports?
To read: * https://danwalsh.livejournal.com/74095.html * bmuschko/gradle-docker-plugin#890 Maybe it's because of multiple port exports?
To read: * https://danwalsh.livejournal.com/74095.html * bmuschko/gradle-docker-plugin#890 Maybe it's because of multiple port exports?
Hi,
Thanks for this useful plugin.
Is there a way to specify multiple port. I tried with
hostConfig.portBindings = ["8082:8082","10000:10000"]
But it always takes the last one. Am I missing something here?
The text was updated successfully, but these errors were encountered: