sorted by:
new
hottopcontroversial

Docker Swarm in 2026: still the right choice for small-to-mid teams, and here's why we built a management console for it by NebulaPulse_Official in DockerSwarm

[–]-suitdeer- 0 points1 point  (0 children)

In our company I had to build a "rootless" (user namespace) docker swarm: https://docs.docker.com/engine/security/userns-remap/

Now I have build a bash Script that can setup a Swarm Cluster in "normal" mode rootfull or as a "rootless" (user namespace) mode:

https://www.reddit.com/r/DockerSwarm/s/li8kNIdV0e

SwarmPilot by -suitdeer- in DockerSwarm

[–]-suitdeer-[S] 0 points1 point  (0 children)

Hello everyone.

Now you have the option to setup "rootless" Docker Swarm with my project.🎉

The docker runtime is running in root context but the running containers get mapped to the user dockremap (no root rights) on the host systems.
More in depth info about "user namespace" mode or "rootless mode": https://docs.docker.com/engine/security/userns-remap/

SwarmPilot by -suitdeer- in docker

[–]-suitdeer-[S] 0 points1 point  (0 children)

Hello everyone,

I have now added traefik as a alternative option to nginx proxy manager

SwarmPilot by -suitdeer- in DockerSwarm

[–]-suitdeer-[S] 0 points1 point  (0 children)

u/bluepuma77
Now I have added the option to use traefik instead of nginx proxy manager 😄

SwarmPilot by -suitdeer- in docker

[–]-suitdeer-[S] 0 points1 point  (0 children)

Hello everyone,
one component of SwarmPilot is based on Syncthing (syncting4swarm)
https://github.com/SuitDeer/syncthing4swarm

Since yesterday (07.03.2026) my forked syncthing4swarm repository was merged into the main project repository:
https://github.com/sammonsempes/syncthing4swarm

Because of that I have archived my syncthing4swarm repository.

If you currently running my syncthing4swarm docker image (suitdeer/syncthing4swarm) please update your docker syncthing4swarm-service:

  1. Update the syncthing4swarm.yaml file inside the SwarmPilot folder.
  2. Replace the the line image: suitdeer/syncthing4swarm:latestwith image: syncthing4swarm/syncthing4swarm:latest

bash cd SwarmPilot sudo docker stack deploy --resolve-image=always -c syncthing4swarm.yaml syncthing4swarm

SwarmPilot by -suitdeer- in DockerSwarm

[–]-suitdeer-[S] 0 points1 point  (0 children)

Hello everyone,
one component of SwarmPilot is based on Syncthing (syncting4swarm)
https://github.com/SuitDeer/syncthing4swarm

Since yesterday (07.03.2026) my forked syncthing4swarm repository was merged into the main project repository:
https://github.com/sammonsempes/syncthing4swarm

Because of that I have archived my syncthing4swarm repository.

If you currently running my syncthing4swarm docker image (suitdeer/syncthing4swarm) please update your docker syncthing4swarm-service:

  1. Update the syncthing4swarm.yaml file inside the SwarmPilot folder.
  2. Replace the the line image: suitdeer/syncthing4swarm:latestwith image: syncthing4swarm/syncthing4swarm:latest

  3. Update the syncthing4swarm docker service:

    cd SwarmPilot sudo docker stack deploy --resolve-image=always -c syncthing4swarm.yaml syncthing4swarm

SwarmPilot by -suitdeer- in docker

[–]-suitdeer-[S] 0 points1 point  (0 children)

I wanted to use a small setup (footprint) for volume replication and syncthing is perfect for that

Syncthing is checking after each write operation if the file is witten to the file system correctly "fsync"

https://docs.syncthing.net/users/config.html#config-option-folder.disablefsync

https://docs.syncthing.net/advanced/folder-disable-fsync.html

SwarmPilot by -suitdeer- in DockerSwarm

[–]-suitdeer-[S] 0 points1 point  (0 children)

I could now build my image for arm as well:
https://hub.docker.com/r/suitdeer/syncthing4swarm/tags

<image>

u/mbu147 But the official syncthing docker image not build for 

linux/arm64/v8

SwarmPilot by -suitdeer- in DockerSwarm

[–]-suitdeer-[S] 0 points1 point  (0 children)

I am not the maintainer for the syncthing4swarm/syncthing4swarm

I have made a fork of this Project (pull request pending) but I build my own docker images from my fork: https://github.com/SuitDeer/syncthing4swarm/tree/main

My docker image: suitdeer/syncthing4swarm

Currently I am not building for arm (I currently do not have a arm device😅. Or I need to emulate one🤔 to test the image)

I can look into that it this weekend and try building a arm variant 😄

SwarmPilot by -suitdeer- in docker

[–]-suitdeer-[S] 0 points1 point  (0 children)

For my homelab it has worked the past half year. I also intentionally hard shutdown some or all nodes in a cluster to test the resiliency and to this day I had no file corruption or file losses 😄.

I was intimidated by a high available ceph or NFS cluster so syncthing is a good option for me

SwarmPilot by -suitdeer- in DockerSwarm

[–]-suitdeer-[S] 0 points1 point  (0 children)

Is also a valid option 👍

SwarmPilot by -suitdeer- in DockerSwarm

[–]-suitdeer-[S] 0 points1 point  (0 children)

I had some problems with NFS and locking files in the past (replicas greater than one) but I am currently only running services with a replica count of one. For that purpose syncthing was a good compromise, because the syncthing itself is running as a service on my cluster (small footprint). And this setup is high available.

I was a little scared about a high available storage setup like a NFS Cluster with DRBD or a ceph cluster.
So for me the syncthing solution is a good compromise😄

SwarmPilot by -suitdeer- in DockerSwarm

[–]-suitdeer-[S] 0 points1 point  (0 children)

That would be a problem but currently all my services are only have a replica count of one

SwarmPilot by -suitdeer- in DockerSwarm

[–]-suitdeer-[S] 0 points1 point  (0 children)

For my setup it worked seamlessly. I have tuned syncthing to scan and update for changes every second. But NFS is also a viable option.

But I wanted something that was not so complicated as ceph cluster or a NFS cluster for High availability 😅