Skip to content

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

Description

@ramizrshaik

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:thin@30.40.50.60: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 :)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions