-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
port_map doesn't work #472
Comments
Thanks for the report. Can you show me the task config you're using? There was a similar PR merged this morning to fix the wrong port being exposed but it looked like |
I think that #466 is exactly what I am experiencing. for what its worth I have been trying a few different task but I was unable to even get this example.nomad to work I get the same looking port map as in #466
|
@ChrisMcKenzie This is already fixed in master, we will release a binary of 0.2.1 this Friday, in the meantime let us know if you see any other issues. |
Thanks so much! |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
I maybe misunderstanding but when I configure the
port_map
section oftask.config
it should take the ports given in that map and use them as the port the port that I am listening on in my container and map it to the port that was randomly selected on the host. If this correct it does not appear to be doing that it expose the port from the map but it is not mapped to the host portsdocker reports the following ports
![](https://camo.githubusercontent.com/a26d4cee3ed17aecf72c622ffb024d9dbfa405ff890d5b3603a87085d71ce300/687474703a2f2f73686172652e63687269736d636b656e7a69652e696f2f312e5f746d75785f323031352d31312d31395f31342d35332d33372e706e67)
Note: this is happening with even the example.nomad generated by running nomad init
The text was updated successfully, but these errors were encountered: