-
Notifications
You must be signed in to change notification settings - Fork 14
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
(fix) use network_mode host for Docker driver #2
base: main
Are you sure you want to change the base?
Conversation
This is because the configuration causes the application to try to reach out to the local host (127.0.0.1) but the Docker driver defaults to bridge mode. By explicitly defining host in the config we can reach the redis instance.
Thanks! It indeed fixed the issue I had with jobs not able to connect to the Redis server (as described in #3). |
Hey all, thanks so much for your interest and help in improving the get started guides! We updated the guide about a month ago with new instructions that help with the issue around local Docker networking with The Create the cluster section has information about networking with @gmemstr could you try out the updated guide and see if it works for you? If so, we can close this as resolved. Thanks! |
@tunzor Thank you for the insights. I just want to give the hint, that the guide about the pytechco jobs still refers to using the cluster ip address instead of localhost to reach the web ui. I guess this causes the main problems in this scenario. Would't it be better to also update this guide to refer to http://localhost:5000 for visiting the simulation web ui? |
Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement Learn more about why HashiCorp requires a CLA and what the CLA includes Have you signed the CLA already but the status is still pending? Recheck it. |
@tunzor thanks for the added section. On Mac with Homebrew, a service was auto created and started for me. I had erroneously assumed that this service would be bound similar to the example but had to go back. Not sure if it's worth a callout but it was an extra step and some troubleshooting for me. |
Personnaly i'm unable to make the tutorial work. Spent already 3h trying to figure it out, make it all work, change the Docker network mode to "host", but the then the |
This is because the configuration causes the application to try to reach out to the local host (127.0.0.1) but the Docker driver defaults to bridge mode. By explicitly defining host in the config we can reach the redis instance.
I don't know if this was intentional, or a misconfiguration of my setup, but out of the box the examples don't seem to work :)