This repository was archived by the owner on Dec 13, 2019. It is now read-only.
Repository navigation
This repository was archived by the owner on Dec 13, 2019. It is now read-only.
DNS/Networking #1
Description
Hi,
thanks for that great example dev-environment!
You mention in the Readme a desire for help with the DNS/network setup:
If you are a Docker Guru, please help me with this DNS related tasks. How to resolve logical container names between networks.... ?
I didn't really understand what you mean, can you provide more details, please?
If I understand your question correctly it's not about providing container names via DNS for access from outside Docker, but more about cross-network communication? Have you considered to add another network and put every container inside that network, in addition to the smaller networks?
This one might help: https://docs.docker.com/engine/userguide/networking/#embedded-dns-server
Activity
svenruppert commentedon Jan 24, 2018
Good morning,
just saw your message here. Excuse my delay , please.
Yes you are right, I need help with the solution to provide the cross network communication.
The challenge here: Drone will create for every build step a new container in a different network. I want to use symbolic names inside the Docker universe instead of the external IP´s. But I was not able to put all components into the general bridge network.. But maybe we could have a small chat about it if you agree and you have some time.