Chapter 14.4 - Simulate Docker Node1 Failure - After leaving swarm, cannot do "docker node update" or "docker node ls"
brian4ko opened this issue · comments
Exercise
Chapter 14.4 - Try It Now - Simulate Node1 Failure - page 267
Problem
On node2 (or any node for that matter), i cannot execute successfully:
docker node update --availability active node5
I also cannot do docker node ls on any of the five nodes. So essentially, I have no idea who is the Leader anymore or can tell who is. Seems like a pretty straight forward exercise. Have the docker rules changed now?
Docker version
Client:
Cloud integration: v1.0.29
Version: 20.10.17
API version: 1.41
Go version: go1.17.11
Git commit: 100c701
Built: Mon Jun 6 23:09:02 2022
OS/Arch: windows/amd64
Context: default
Experimental: true
Server: Docker Desktop 4.12.0 (85629)
Engine:
Version: 20.10.17
API version: 1.41 (minimum version 1.12)
Go version: go1.17.11
Git commit: a89b842
Built: Mon Jun 6 23:01:23 2022
OS/Arch: linux/amd64
Experimental: true
containerd:
Version: 1.6.8
GitCommit: 9cd3357b7fd7218e4aec3eae239db1f68a5a6ec6
runc:
Version: 1.1.4
GitCommit: v1.1.4-0-g5fd4c4d
docker-init:
Version: 0.19.0
GitCommit: de40ad0
Resolved the issue. There was none. Did not join node2 and 3 as managers originally.