Single node cluster : "This node is not a swarm manager"
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3.7k
- Forks
- 676
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 6
Description
Message
Swarm: error
NodeID:
Error: manager stopped: can't initialize raft node: irreparable WAL error: wal: max entry size limit exceeded, recBytes: 3772, fileSize(64000000) - offset(63998024) - padBytes(4) = entryLimit(1972)
Details
[ec2-user@ip-10-0-1-213 ~]$ docker info
Client:
Version: 25.0.3
Context: default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.0.0+unknown
Path: /usr/libexec/docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.29.1
Path: /home/ec2-user/.docker/cli-plugins/docker-compose
Server:
Containers: 15
Running: 15
Paused: 0
Stopped: 0
Images: 22
Server Version: 25.0.3
Storage Driver: overlay2
Backing Filesystem: xfs
Supports d_type: true
Using metacopy: false
Native Overlay Diff: true
userxattr: false
Logging Driver: json-file
Cgroup Driver: systemd
Cgroup Version: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
Swarm: error
NodeID:
Error: manager stopped: can't initialize raft node: irreparable WAL error: wal: max entry size limit exceeded, recBytes: 3772, fileSize(64000000) - offset(63998024) - padBytes(4) = entryLimit(1972)
Is Manager: false
Node Address: 10.0.1.213
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 64b8a811b07ba6288238eefc14d898ee0b5b99ba
runc version: 4bccb38cc9cf198d52bebf2b3a90cd14e7af8c06
init version: de40ad0
Security Options:
seccomp
Profile: builtin
cgroupns
Kernel Version: 6.1.87-99.174.amzn2023.x86_64
Operating System: Amazon Linux 2023.4.20240429
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 15.41GiB
Name: ip-10-0-1-213.eu-west-2.compute.internal
ID: 92e389d2-a806-4abd-a531-549c2158b697
Docker Root Dir: /var/lib/docker
Debug Mode: false
Experimental: true
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report names no source file, test, or reproduction steps beyond the docker info output. Start by tracing manager initialization around raft and WAL handling, then determine how the reported irreparable WAL error should be handled and what test would demonstrate the intended behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100