Tukukkk

I'm trying to configure on AWS a docker swarm example.

I have three machines: two nodes and on manager, created by using docker-machine:

docker-machine create --driver amazonec2 --amazonec2-region eu-central-1 swarm-manager

docker-machine create --driver amazonec2 --amazonec2-region eu-central-1 docker1

docker-machine create --driver amazonec2 --amazonec2-region eu-central-1 docker2

I set up docker1 and 2 like this:

set up /etc/default/docker:

DOCKER_OPTS="-H tcp://0.0.0.0:2375 -H unix:///var/run/docker.sock"

rebooted docker and then:

sudo docker run -d swarm join --addr=172.31.5.27:2375 token://<token>

and checked it:

ubuntu@docker1:~$ sudo docker ps

CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS               NAMES

a4ae06e827a6        swarm               "/swarm join --addr=1"   28 minutes ago      Up 28 minutes       2375/tcp            admiring_blackwell

on the swarm machine:

sudo docker run -dP swarm manage token://

and I added my nodes:

ubuntu@swarm-manager:~$ sudo docker ps

CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS                     NAMES

67f55fda2eba        swarm               "/swarm manage token:"   16 minutes ago      Up 16 minutes       0.0.0.0:32768->2375/tcp   trusting_dijkstra



ubuntu@swarm-manager:~$ docker -H tcp://127.0.0.1:32768 info

Containers: 0

 Running: 0

 Paused: 0

 Stopped: 0

Images: 0

Server Version: swarm/1.2.5

Role: primary

Strategy: spread

Filters: health, port, containerslots, dependency, affinity, constraint

Nodes: 2

 (unknown): 172.31.11.143:2375

  └ ID:

  └ Status: Pending

  └ Containers: 0

  └ Reserved CPUs: 0 / 0

  └ Reserved Memory: 0 B / 0 B

  └ Labels:

  └ Error: Cannot connect to the Docker daemon. Is the docker daemon running on this host?

  └ UpdatedAt: 2016-10-29T16:34:28Z

  └ ServerVersion:

 (unknown): 172.31.5.27:2375

  └ ID:

  └ Status: Pending

  └ Containers: 0

  └ Reserved CPUs: 0 / 0

  └ Reserved Memory: 0 B / 0 B

  └ Labels:

  └ Error: Cannot connect to the Docker daemon. Is the docker daemon running on this host?

  └ UpdatedAt: 2016-10-29T16:34:38Z

  └ ServerVersion:

Plugins:

 Volume:

 Network:

Swarm:

 NodeID:

 Is Manager: false

 Node Address:

Security Options:

Kernel Version: 4.2.0-18-generic

Operating System: linux

Architecture: amd64

CPUs: 0

Total Memory: 0 B

Name: 67f55fda2eba

Docker Root Dir:

Debug Mode (client): false

Debug Mode (server): false

WARNING: No kernel memory limit support

I can't undersrtand why imy nodes are still pending. The private IPs I used seem to be correct, plus the two nodes are listes. Any hint?

This may be related to this issue. My understanding is that there's a problem with docker machines created with Docker 1.12.1. The error that I'm getting is

Error checking TLS connection: "mybox" is not a swarm master. The --swarm flag is intended for use with swarm masters

after running

eval $(docker-machine env --swarm mybox)

You may be arriving at the same problem via slightly different route but I'm having the same issue of the swarm not forming.

You need to login to the swarm manager using docker-machine ssh aws-swarm-mgr, and initiate
docker-swarm init on the master node first.

then login to the slave nodes using
docker-machine ssh docker1

Please note the token to join the master here, example output

docker swarm join --token SWMTKN-1-65v85za1nnkg4u09e1jbgtk86b3pl8ntawj0ha6m6upzbyho5z-4fasp7wt5f13ts16arypbrpa1 192.168.99.100:2377

and run from docker1 node and docker2 node

docker swarm join --token xxxLOREMIPSUMTOKENx ip:2377

To confirm the above, login to the master node

docker-machine ssh aws-swarm-mgr

From within, the master aws node

aws-swarm-mgr> docker node ls

That should do it.

I have a docker swarm on AWS with three nodes. I should see my web page through any three public IP address. I have opened the required security group stated on docker doc. I think they have this bug for their overlay driver...