-
Notifications
You must be signed in to change notification settings - Fork 90
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
Issue with DNS names on different levels #91
Comments
I am working on this issue. This is a little bit more difficult than what I was expected to. |
Ok, hope when you fix it you publish new built version on docker hub with #85 fix as well |
I also ran into this - for now my workaround is to not use tiered aliases for different services. Looking forward to the fix, let me know if I can help in some way. |
hey, are you going to finish this? would be grateful for this. |
Hi, guys! |
Hi @aacebedo do you have any input on this issue? |
docker-compose.yaml
contains two services with such definitions (stuff omitted)service-client container got IP 172.19.0.5
service container got IP 172.19.0.3
both address return two IP's:
The text was updated successfully, but these errors were encountered: