-
Notifications
You must be signed in to change notification settings - Fork 6
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
Suggestion: Use some defaults when linking containers #6
Comments
could you please describe with some example, how would you use those variables when linking docker containers? It's not clear to me yet :) |
I'm kind of new to the whole docker thingy, but I think those variables are set if you link the elasticsearch and mongodb container with the
In the mongo2es container, those variables are accessible, I think. If those are available you could set the |
so if I understand, docker automatically creates those env variables for you if you |
Awesome :) maybe I'll investigate further next week, which kind of other variables being set and so on. My hands are quite tightened this week while working on my master thesis. |
@Alino I looked into this anyway. Created a two PR's for you to take a look at :) |
Good job, I just merged your PRs, but I am not sure about this one, I haven't tested it yet. Did you try it, or are you using this approach? is everything ok with it? Maybe I should keep it opened, and test it later |
Haven't got the time to test it thoroughly yet, sorry. |
For the simplicity, when linking containers, use env variables like below if no other env variable is set.
MONGO_PORT_27017_TCP_ADDR
andMONGO_PORT_27017_TCP_PORT
ELASTICSEARCH_PORT_9200_TCP_ADDR
andELASTICSEARCH_PORT_9200_TCP_PORT
The text was updated successfully, but these errors were encountered: