35
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 17 May 2026
35 points (100.0% liked)
Selfhosted
59263 readers
1461 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
I'm running dokploy in swarm mode on 3 nodes.
The only downside is the development of swarm is basically halted and some features are missing (like passing /dev devices to a container, you have to use dirty workarounds) but otherwise it just works.
And another thing I have not heard yet. Dokploy looks really enticing just from a brief look at their site, I'll definitely add it to my list of things to look into. Thank you!
How long have you been running this type of setup?
How is swarm support/integration with Dokploy? Are you able to initiate the swarm and also connect other docker nodes to that swarm all through the webgui or does Dokploy just see and attach to the swarm after its been setup? Are you able to manage it all through the gui? Swing/motion containers to other nodes, etc.
I'll definitely need to deploy it in a test environment and see how it all works. Thank you again!
I've been running it for 2 years.
The swarm support integration is first class, but there is not much to do in the gui, you can add nodes and see basic info about them and thats it basically.
Most of the stuff happens in the compose files where you can define how many copies of a container you run and what nodes you want to restrict them to. etc.
I'm not sure about the moving features tbh. It should move them automatically when a node is down. In my setup I don't use that at all, all my containers are pinned to specific nodes by feature flags (one node has lots of hdd storage, another has more ram, another has a gpu).
You can see the container logs, but you have to select "swarm" in a dropdown when the container is not on your master node.
And also when deploying a new app you have to select "Compose" and then in a further dropdown "Swarm".