WARNING: No memory limit support
WARNING: No swap limit support
WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support
WARNING: No cpu shares support
WARNING: No cpuset support
WARNING: No io.weight support
WARNING: No io.weight (per device) support
WARNING: No io.max (rbps) support
WARNING: No io.max (wbps) support
WARNING: No io.max (riops) support
WARNING: No io.max (wiops) support
pi@rpi4b-node1:~ $ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
Feb 05 22:45:51 rpi4b-node1 systemd[1]: Starting Docker Application Container Engine...
░░ Subject: A start job for unit docker.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit docker.service has begun execution.
░░
░░ The job identifier is 785.
Feb 05 22:45:51 rpi4b-node1 dockerd[5265]: time="2022-02-05T22:45:51.791215754Z" level=info msg="Starting up"
Feb 05 22:45:51 rpi4b-node1 dockerd[5265]: time="2022-02-05T22:45:51.794370451Z" level=info msg="parsed scheme: \"unix\"" module=grpc
Feb 05 22:45:51 rpi4b-node1 dockerd[5265]: time="2022-02-05T22:45:51.794964144Z" level=info msg="scheme \"unix\" not registered, fallback to default scheme" module=grpc
Feb 05 22:45:51 rpi4b-node1 dockerd[5265]: time="2022-02-05T22:45:51.795432412Z" level=info msg="ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock <nil> 0 <nil>}] <nil> <nil>}" module=grpc
Feb 05 22:45:51 rpi4b-node1 dockerd[5265]: time="2022-02-05T22:45:51.795851348Z" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc
Feb 05 22:45:51 rpi4b-node1 dockerd[5265]: time="2022-02-05T22:45:51.799685625Z" level=info msg="parsed scheme: \"unix\"" module=grpc
Feb 05 22:45:51 rpi4b-node1 dockerd[5265]: time="2022-02-05T22:45:51.800263447Z" level=info msg="scheme \"unix\" not registered, fallback to default scheme" module=grpc
Feb 05 22:45:51 rpi4b-node1 dockerd[5265]: time="2022-02-05T22:45:51.800685347Z" level=info msg="ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock <nil> 0 <nil>}] <nil> <nil>}" module=grpc
Feb 05 22:45:51 rpi4b-node1 dockerd[5265]: time="2022-02-05T22:45:51.801166411Z" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc
Feb 05 22:45:51 rpi4b-node1 dockerd[5265]: time="2022-02-05T22:45:51.976702501Z" level=info msg="[graphdriver] using prior storage driver: overlay2"
Feb 05 22:45:51 rpi4b-node1 dockerd[5265]: time="2022-02-05T22:45:51.983444276Z" level=warning msg="Unable to find memory controller"
Feb 05 22:45:51 rpi4b-node1 dockerd[5265]: time="2022-02-05T22:45:51.984003691Z" level=info msg="Loading containers: start."
Feb 05 22:45:52 rpi4b-node1 dockerd[5265]: time="2022-02-05T22:45:52.714349982Z" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address"
Feb 05 22:45:52 rpi4b-node1 dockerd[5265]: time="2022-02-05T22:45:52.969587608Z" level=info msg="Loading containers: done."
Feb 05 22:45:53 rpi4b-node1 dockerd[5265]: time="2022-02-05T22:45:53.106122071Z" level=info msg="Docker daemon" commit=459d0df graphdriver(s)=overlay2 version=20.10.12
Feb 05 22:45:53 rpi4b-node1 dockerd[5265]: time="2022-02-05T22:45:53.106324826Z" level=info msg="Daemon has completed initialization"
Feb 05 22:45:53 rpi4b-node1 systemd[1]: Started Docker Application Container Engine.
░░ Subject: A start job for unit docker.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit docker.service has finished successfully.
░░
░░ The job identifier is 785.
Feb 05 22:45:53 rpi4b-node1 dockerd[5265]: time="2022-02-05T22:45:53.241236784Z" level=info msg="API listen on /run/docker.sock"
pi@rpi4b-node1:~ $ docker node list
ID HOSTNAME STATUS AVAILABILITY MANAGER STATUS ENGINE VERSION
tdfutddkxmjyxz3bsudtdwh4z * rpi4b-node1 Ready Active Leader 20.10.12
Please, use the </> button to insert codes, commands and logs because the markdown filter hides potentially important parts of them if you just quote. I edited your post to fix it.
Is the logs from right after you initialized the manager node? I don’t see any swarm log, only how Docker started.
If you remove your manager from the cluster (``docker swarm leave --force`) and try to set the listen address instead of the advertise address, you can make sure you are checking the right port:
I’m having the same issue too. I have a raspberry pi host and cannot connect to it from another pi or from my Mac. The biggest red flag that swarm is failing to listen on that port is that I’m able to run the python webserver on 2377 even when it’s supposedly waiting for connections.
I have exactly the same problem. I have installed Docker and activated rootless setup. After some research, I found out that swarm mode and rootless mode are not possible together.
From the documentation:
When you initialize a swarm or join a Docker host to an existing swarm, an overlay network called ingress is created on that Docker host, which handles the control and data traffic related to swarm services.
Run the Docker daemon as a non-root user overlay networks are not supported.
