Skip to content
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

Closed
ghost opened this issue Nov 23, 2019 · 6 comments
Closed

Multiple port in hostConfig.portBindings doesn't work #890

ghost opened this issue Nov 23, 2019 · 6 comments
Assignees

Comments

@ghost
Copy link

ghost commented Nov 23, 2019

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?

@orzeh orzeh self-assigned this Nov 24, 2019
@orzeh
Copy link
Collaborator

orzeh commented Nov 24, 2019

@rocks4530 your example should work. Can you create a minimal repo/example which demonstrates the issue?

@ghost
Copy link
Author

ghost commented Nov 27, 2019

HI @orzeh ,
please check this example @
https://github.com/rocks4530/envoy-proxy

docker ps commands shows this

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
483f45f7a901 6f923718edf9 "/docker-entrypoint.…" 12 minutes ago Up 12 minutes 0.0.0.0:10000->10000/tcp envoy-proxy

@orzeh orzeh added the bug label Nov 27, 2019
@orzeh
Copy link
Collaborator

orzeh commented Nov 27, 2019

@rocks4530 ok, I can reproduce it with your example. I need some time to dig into this.

@orzeh orzeh changed the title Define multiple port in hostConfig.portBindings Multiple port in hostConfig.portBindings doesn't work Nov 27, 2019
@ghost
Copy link
Author

ghost commented Nov 27, 2019

@orzeh thanks.

@orzeh
Copy link
Collaborator

orzeh commented Nov 30, 2019

@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.

@orzeh orzeh closed this as completed Nov 30, 2019
@orzeh orzeh removed the bug label Nov 30, 2019
@ghost
Copy link
Author

ghost commented Dec 1, 2019

good to know that. And thanks. Will try out to see.

dagguh added a commit to dagguh/infrastructure that referenced this issue Apr 12, 2021
dagguh added a commit to dagguh/infrastructure that referenced this issue May 7, 2021
dagguh added a commit to atlassian/infrastructure that referenced this issue Mar 3, 2023
mgrzaslewicz pushed a commit to atlassian/infrastructure that referenced this issue Sep 7, 2023
mgrzaslewicz pushed a commit to atlassian/infrastructure that referenced this issue Sep 7, 2023
dagguh added a commit to atlassian/infrastructure that referenced this issue Sep 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant