Skip to content
This repository has been archived by the owner on Sep 7, 2023. It is now read-only.

Trying to communicate with the external ip into my docker consul #121

Open
ssboopathi opened this issue Apr 10, 2019 · 0 comments
Open

Trying to communicate with the external ip into my docker consul #121

ssboopathi opened this issue Apr 10, 2019 · 0 comments

Comments

@ssboopathi
Copy link

ssboopathi commented Apr 10, 2019

I am new for docker and consul. I have created the 4 instances in AWS. I have added the use of the following instance.
First Instance - Server 1
Second Instance - Server 2
Third Instance - Server 3
Fourth Instance - Server 4

This instance having the ubuntu 18.04 OS. I am trying to implement an auto-discovery concept using consul.

I have done the following steps.

I have installed the docker in my four instances using the below link https://docs.docker.com/install/linux/docker-ce/ubuntu/

And pulling the consul image using the below link

https://hub.docker.com/_/consul?tab=description

I have checked on 'Running Consul for Development'. Its working fine for all the instances.

Server 1:

I am trying to run on consul agent in client mode. It's showing below error.

sudo docker run -d --net=host -e 'CONSUL_LOCAL_CONFIG={"leave_on_terminate": true}' consul agent -bind= -retry-join=

- I have given on server1 private IP.
- I have given on bootstrap server private IP.

Output:
I got the 64 letter key. EG: b93b160ef52b9203d67bb6db27793963dc419276145f4c247c9ba4e2bd6deb03

But that reference sites having a different response.

dig @bootstrap_server_private_ip -p 8600 consul.service.consul

It's showing on connection timed out the error.
https://ibb.co/ZKVPDtD

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

No branches or pull requests

1 participant