-
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
runing multiple instances (count) allocate same dynamic port #492
Comments
definitely in v0.2.0, I'm trying now against master... |
and the same in master |
@sielaq: Thanks for reporting. Confirmed it as a bug and we are working on a fix now |
Can confirm a nomad binary built from master solves this problem 👍 |
This is a follow-up to hashicorp#483
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. |
Hi there,
try nomad init example with
count = 2
(where no example was running before)
you will see error like this:
Same if you want to scale up (from 1 to 4) it will spawn only one new container, and 2 gonna be failed.
seems like it allocate dynamic port for every instances.
The text was updated successfully, but these errors were encountered: