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

re: Unable resolve interlock to target host on which oracle container is running #242

Open
ramizrshaik opened this issue Sep 20, 2017 · 0 comments

Comments

@ramizrshaik
Copy link

Hi,

i am spawned and oracle container in docker swarm and i used a interlock label for that container.

my docker compose file
2017-09-20_12-04-58

so there is an server in the middle to maintain all the interlock names. the problem is when i try to use my interlock name 'pm-int-test-**' as part of oracle url 'jdbc:oracle:thin@pm-int-test:1521:xe' its not resolving into target host.

lets the my container is running on 10.11.123.125:1521

but when i do 'tnsping pm-int-test-**' its is giving me that intelock maintaing server address in 'jdbc:oracle:[email protected]:1521:xe' and saying there is no TNS listener here. 30.40.50.60 is address of interlock maintaining server.

can any one please help me on how to use interlock that will directly resolve to host '10.11.123.125 ' on which my container is running.

thanks in advance :)

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