can't run under fig about docker-consul HOT 8 CLOSED

To anyone who finds this issue, setting -data-dir /tmp/consul in your consul command: will resolve the issue.

from docker-consul.

Ok it seems that if I restart it like this

$ fig stop
$ fig rm
$ fig up

It works.

from docker-consul.

Not sure why that would do it. This works consistently?

On Mon, Nov 10, 2014 at 1:56 PM, Scott Robertson [email protected]
wrote:

Ok it seems that if I restart it like this

$ fig stop
$ fig rm
$ fig up

It works.

—
Reply to this email directly or view it on GitHub
#35 (comment)
.

Jeff Lindsay
http://progrium.com

from docker-consul.

It does it because fig just restarts the containers, and doesn't recreate them unless you tell it to.

Docker will bring the machines up on new IP addresses - and the existing consul state from the first run tells it to look for cluster mates that no longer exist.

from docker-consul.

I think that this is something that should be addressed in fig. I'm not quite sure what would have to be done on their end though...

from docker-consul.

Encountered this too and I can confirm removing containers (using docker-compose rm) works. It's unfortunate we need this though.

@mileswilson mentions docker compose just restarts containers but doesn't recreate them. At least in the latest version of docker-compose the opposite is true. docker-compose up will recreate containers unless --no-recreate is passed as an argument. Nevertheless this doesn't change the issue at all since consul's cluster state still appears to be stale and only running docker-compose rm first resolves the issue.

from docker-consul.

This is just the way that Consul works. The state (containing the correct IP address of Consul self) is persisted because docker-compose does not remove the container. When the container is restarted, it has a new IP address. This would be a feature request for docker-compose.

from docker-consul.

A quick fix is also to remove peers.json, especially if you've mounted a data volume. Say your data volume is mounted at /mnt/consul, just remove /mnt/consul/raft/peers.json when consul has been stopped and it should re-establish communications.

from docker-consul.