Skip to content
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

Container not accesible by hostname by application #37

Closed
nicovillanueva opened this issue Aug 14, 2015 · 1 comment
Closed

Container not accesible by hostname by application #37

nicovillanueva opened this issue Aug 14, 2015 · 1 comment

Comments

@nicovillanueva
Copy link

My issue is essentially, exactly this one: crosbymichael/skydock#92

I have a set of Dockers running: dnsdock, a Redis server, and a Scala Play app.

All of their hostnames are resolved correctly when, for example, using redis-cli from my local machine, or pinging from one another.

The problem is that when the Play app connects to the Redis server, it cannot resolve it's hostname (but it can connect to it using the container's IP)

Dig (and ping, and redis-cli) resolves the hostname just fine:
dig @172.17.42.1 +short redis-dev.redis.docker
172.17.0.6

But I can't get the application to do so.
Trying a connection through the Python3 REPL (using the pymongo package) yields the same result.

EDIT: Adding that I'm using Linux Mint 17.2 as my host, and Ubuntu 14.02 in my Play application.

@nicovillanueva
Copy link
Author

"Fixed"
Note that the latest tag doesn't work, and presents the symptoms above described.
You just have to use the tag v1.10.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant