-
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
[question] docker -netalias or alternative #2105
Comments
@jrusiecki There is a PR out there which allows users to pass the net alias to the docker daemon. Once that is merged this would be possible. |
Fixed by #1980 |
Thx, will try :) |
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. |
Nomad 0.5.0, Consul 0.7.1, Docker 1.12
I use docker overlay network between containers. To find other container to connect to I use docker built-in DNS. It allows me to lookup IP of node (e.g. elastic01) by node name. But with nomad name is unpredictable. I've read -netalaist parameter to docker run solves the problem - but HOW to specify -netalias for docker with job specification?
The text was updated successfully, but these errors were encountered: