Docker Swarm Support #19

Open
opened 2025-10-31 14:59:50 -05:00 by GiteaMirror · 25 comments
Owner

Originally created by @iLuckyW on GitHub (Aug 18, 2024).

Is there a plan to support docker swarm? Would be really interested to replace portainer with monitor as a tool to monitor a docker swarm.

Originally created by @iLuckyW on GitHub (Aug 18, 2024). Is there a plan to support docker swarm? Would be really interested to replace portainer with monitor as a tool to monitor a docker swarm.
GiteaMirror added the enhancement label 2025-10-31 14:59:50 -05:00
Author
Owner

@mbecker20 commented on GitHub (Aug 18, 2024):

Good point, yes I think this would be very nice, I'll add it to the roadmap near Kubernetes support.

@mbecker20 commented on GitHub (Aug 18, 2024): Good point, yes I think this would be very nice, I'll add it to the roadmap near Kubernetes support.
Author
Owner

@mrvalterhugo commented on GitHub (Sep 7, 2024):

This would be very nice to have, I run a swarm cluster in my proxmox server, using LXC containers.
Portainer supports it and it is useful.

@mrvalterhugo commented on GitHub (Sep 7, 2024): This would be very nice to have, I run a swarm cluster in my proxmox server, using LXC containers. Portainer supports it and it is useful.
Author
Owner

@Surrogard commented on GitHub (Sep 13, 2024):

I would be very interested in this as well. I have a 12 node Docker swarm, so portainer is out for me.

If you need help with anything, just ping me.

@Surrogard commented on GitHub (Sep 13, 2024): I would be very interested in this as well. I have a 12 node Docker swarm, so portainer is out for me. If you need help with anything, just ping me.
Author
Owner

@mikemilligram commented on GitHub (Nov 4, 2024):

Also interested in this, running swarm across four nodes. I'm by no means an expert but I'd love to help out in any way possible!

@mikemilligram commented on GitHub (Nov 4, 2024): Also interested in this, running swarm across four nodes. I'm by no means an expert but I'd love to help out in any way possible!
Author
Owner

@TC74 commented on GitHub (Feb 25, 2025):

Docker swarm support is a good (must) feature to have, as there is no alternative out there other than Portainer. You can make it free, and sell entreprise support to fund this project.

IMO, focus on docker stack and swarm will make komo.do the go to solution for docker goer that is looking for simple setup. Swarmpit was the go to, but the project is now dead. Rancher stopped supporting Docker Swarm. Portainer basically need to purchase licenses (I was willing to pay, but does not like the license based charging model... hahaha).

Looking forward to Docker Stack and Swarm support.

@TC74 commented on GitHub (Feb 25, 2025): Docker swarm support is a good (must) feature to have, as there is no alternative out there other than Portainer. You can make it free, and sell entreprise support to fund this project. IMO, focus on docker stack and swarm will make komo.do the go to solution for docker goer that is looking for simple setup. Swarmpit was the go to, but the project is now dead. Rancher stopped supporting Docker Swarm. Portainer basically need to purchase licenses (I was willing to pay, but does not like the license based charging model... hahaha). Looking forward to Docker Stack and Swarm support.
Author
Owner

@StefanSa commented on GitHub (Jun 2, 2025):

@mbecker20
Supporting Docker Swarm is a crucial feature for Komodo, as it fills a gap in the market with no real alternatives besides Portainer.
By integrating Docker Swarm support, Komodo can become the go-to solution for Docker users seeking a simple setup

@StefanSa commented on GitHub (Jun 2, 2025): @mbecker20 Supporting Docker Swarm is a crucial feature for Komodo, as it fills a gap in the market with no real alternatives besides Portainer. By integrating Docker Swarm support, Komodo can become the go-to solution for Docker users seeking a simple setup
Author
Owner

@Sedation6612 commented on GitHub (Jun 8, 2025):

any ETA on swarm support? can't wait to swap once it's added

@Sedation6612 commented on GitHub (Jun 8, 2025): any ETA on swarm support? can't wait to swap once it's added
Author
Owner

@nikhilmaddirala commented on GitHub (Jun 10, 2025):

any ETA on swarm support? can't wait to swap once it's added

It was previously listed on the roadmap for the next version, but now it's moved to "undecided".

@nikhilmaddirala commented on GitHub (Jun 10, 2025): > any ETA on swarm support? can't wait to swap once it's added It was previously listed on the roadmap for the next version, but now it's moved to "undecided".
Author
Owner

@Kieranwest commented on GitHub (Jun 10, 2025):

Would love Docker Swarm support. I'm trying my best to avoid portainer but it seems to be the only option to manage swarms nicely. I guess the only option right now is using the Sync feature of Komodo to replicate the stacks.toml file so i can spin up containers on any node in the event of an outage :(.
Pretty please with a cherry on-top we'd love swarm support <3

@Kieranwest commented on GitHub (Jun 10, 2025): Would love Docker Swarm support. I'm trying my best to avoid portainer but it seems to be the only option to manage swarms nicely. I guess the only option right now is using the Sync feature of Komodo to replicate the stacks.toml file so i can spin up containers on any node in the event of an outage :(. Pretty please with a cherry on-top we'd love swarm support <3
Author
Owner

@mbecker20 commented on GitHub (Jun 10, 2025):

I'm putting it off to solidify the base before adding more features. There have continuously been other pressing features and issues that must be addressed before continuing to expand the scope.

@mbecker20 commented on GitHub (Jun 10, 2025): I'm putting it off to solidify the base before adding more features. There have continuously been other pressing features and issues that must be addressed before continuing to expand the scope.
Author
Owner

@djakupovic commented on GitHub (Jul 1, 2025):

I currently use Komodo with five agents on a 5 node docker swarm cluster as "external" docker servers. This is my main use case for Komodo to deploy "docker compose up" command on specific nodes.

If a swarm feature comes, please give us an option to have docker stack deploy and docker compose up.

Great work so far and thank you for your amazing tool

@djakupovic commented on GitHub (Jul 1, 2025): I currently use Komodo with five agents on a 5 node docker swarm cluster as "external" docker servers. This is my main use case for Komodo to deploy "docker compose up" command on specific nodes. If a swarm feature comes, please give us an option to have docker stack deploy and docker compose up. Great work so far and thank you for your amazing tool
Author
Owner

@Kieranwest commented on GitHub (Jul 1, 2025):

I currently use Komodo with five agents on a 5 node docker swarm cluster as "external" docker servers. This is my main use case for Komodo to deploy "docker compose up" command on specific nodes.

So essentially, you're hosting a Komodo Control Server and then pointing to an external periphery that lives on Docker swarm? If that's the case how does periphery handle creating the Docker containers? Does it run then underneath swarm?

@Kieranwest commented on GitHub (Jul 1, 2025): > I currently use Komodo with five agents on a 5 node docker swarm cluster as "external" docker servers. This is my main use case for Komodo to deploy "docker compose up" command on specific nodes. So essentially, you're hosting a Komodo Control Server and then pointing to an external periphery that lives on Docker swarm? If that's the case how does periphery handle creating the Docker containers? Does it run then underneath swarm?
Author
Owner

@djakupovic commented on GitHub (Jul 2, 2025):

I currently use Komodo with five agents on a 5 node docker swarm cluster as "external" docker servers. This is my main use case for Komodo to deploy "docker compose up" command on specific nodes.

So essentially, you're hosting a Komodo Control Server and then pointing to an external periphery that lives on Docker swarm? If that's the case how does periphery handle creating the Docker containers? Does it run then underneath swarm?

Yes thats how I have done it. Yes it applies docker compose up I assume instead docker stack deploy. This is why I use Komodo. I use portioner for my docker stack - swarm containers - and Komodo for lokal deployments on specific nodes e.g. docker 1 and docker 4

I would like to replace Portainer with Komodo if it has a swarm feature so I need to wait until it is finished. Then portainer is deprecated for me

@djakupovic commented on GitHub (Jul 2, 2025): > > I currently use Komodo with five agents on a 5 node docker swarm cluster as "external" docker servers. This is my main use case for Komodo to deploy "docker compose up" command on specific nodes. > > So essentially, you're hosting a Komodo Control Server and then pointing to an external periphery that lives on Docker swarm? If that's the case how does periphery handle creating the Docker containers? Does it run then underneath swarm? Yes thats how I have done it. Yes it applies docker compose up I assume instead docker stack deploy. This is why I use Komodo. I use portioner for my docker stack - swarm containers - and Komodo for lokal deployments on specific nodes e.g. docker 1 and docker 4 I would like to replace Portainer with Komodo if it has a swarm feature so I need to wait until it is finished. Then portainer is deprecated for me
Author
Owner

@mattsmallman commented on GitHub (Jul 2, 2025):

Just adding a plus 1 for swarm support (when the time is right). I’m a huge fan of komodo and have been trying to get blue/green deployments working for my laravel docker apps but it’s just to messy with multiple stacks and scripts so would prefer to use a docker swarm but don’t want to give up the Komodo interface.

@mattsmallman commented on GitHub (Jul 2, 2025): Just adding a plus 1 for swarm support (when the time is right). I’m a huge fan of komodo and have been trying to get blue/green deployments working for my laravel docker apps but it’s just to messy with multiple stacks and scripts so would prefer to use a docker swarm but don’t want to give up the Komodo interface.
Author
Owner

@Gsyltc commented on GitHub (Jul 4, 2025):

And One more plus.
Dowker swarm support will be a really good feature. Espacally for homelab

@Gsyltc commented on GitHub (Jul 4, 2025): And One more plus. Dowker swarm support will be a really good feature. Espacally for homelab
Author
Owner

@CodeShellDev commented on GitHub (Jul 18, 2025):

Love Komodo sofar would really like to try out Docker Swarm with it. 👍

@CodeShellDev commented on GitHub (Jul 18, 2025): Love Komodo sofar would really like to try out Docker Swarm with it. 👍
Author
Owner

@foureight84 commented on GitHub (Jul 19, 2025):

Another vote for Docker Swarm support

@foureight84 commented on GitHub (Jul 19, 2025): Another vote for Docker Swarm support
Author
Owner

@Deester4x4jr commented on GitHub (Jul 22, 2025):

👍 +1 for this as well. Was going to deploy a container on a test machine with automated caddy reverse proxy, but without overlay networks its a no go. Admittedly a pretty shallow use case, but still would love to have it.

@Deester4x4jr commented on GitHub (Jul 22, 2025): 👍 +1 for this as well. Was going to deploy a container on a test machine with automated caddy reverse proxy, but without overlay networks its a no go. Admittedly a pretty shallow use case, but still would love to have it.
Author
Owner

@syphernl commented on GitHub (Jul 23, 2025):

👍 +1 for this as well. Was going to deploy a container on a test machine with automated caddy reverse proxy, but without overlay networks its a no go. Admittedly a pretty shallow use case, but still would love to have it.

FWIW you already can create swarms and overlay networks by hand (or something like Ansible) and use them within Komodo.
The only thing to keep in mind is to specify this network within your compose files e.g.:


services:
  foo:
    # Your service config here
    networks:
      overlay_network:
        aliases:
          - myservice.svc

networks:
  overlay_network:
    name: overlay_network
    external: true

I have been using this setup for a couple of months now and it is working fine. My containers can communicate with each other over the overlay network across all Docker nodes.
The only thing I noticed is that while Komodo does show the network in the UI clicking it only shows the containers & IP's connected to it from the same node, not on the other nodes.

@syphernl commented on GitHub (Jul 23, 2025): > 👍 +1 for this as well. Was going to deploy a container on a test machine with automated caddy reverse proxy, but without overlay networks its a no go. Admittedly a pretty shallow use case, but still would love to have it. FWIW you already can create swarms and overlay networks by hand (or something like Ansible) and use them within Komodo. The only thing to keep in mind is to specify this network within your compose files e.g.: ```yaml services: foo: # Your service config here networks: overlay_network: aliases: - myservice.svc networks: overlay_network: name: overlay_network external: true ``` I have been using this setup for a couple of months now and it is working fine. My containers can communicate with each other over the overlay network across all Docker nodes. The only thing I noticed is that while Komodo does show the network in the UI clicking it only shows the containers & IP's connected to it from the same node, not on the other nodes.
Author
Owner

@TheLinuxGuy commented on GitHub (Aug 3, 2025):

This feature would be a great addition to komodo, hope it lands soon.

I have been playing with Docker Swarm on 3 nodes with dokploy.com and there are 2 features from dokploy that I wish komodo would get from it:

@TheLinuxGuy commented on GitHub (Aug 3, 2025): This feature would be a great addition to komodo, hope it lands soon. I have been playing with Docker Swarm on 3 nodes with dokploy.com and there are 2 features from dokploy that I wish komodo would get from it: - Docker Swarm - Integrated / automated backups (for [databases](https://docs.dokploy.com/docs/core/databases/backups) and [volumes](https://docs.dokploy.com/docs/core/volume-backups))
Author
Owner

@rkbks commented on GitHub (Aug 25, 2025):

We're planning to move from standalone docker hosts to a swarm setup. Support for docker swarm would be really awesome. We looked at alternatives like Portainer but we don't like how things are going there. Komodo is way superior! Keep up the good work guys.

@rkbks commented on GitHub (Aug 25, 2025): We're planning to move from standalone docker hosts to a swarm setup. Support for docker swarm would be really awesome. We looked at alternatives like Portainer but we don't like how things are going there. Komodo is way superior! Keep up the good work guys.
Author
Owner

@CodeShellDev commented on GitHub (Sep 13, 2025):

This is for Docker Swarm MODE right? Not classic?
Just wanted to make sure...

@CodeShellDev commented on GitHub (Sep 13, 2025): This is for Docker Swarm MODE right? Not classic? Just wanted to make sure...
Author
Owner

@acheslow commented on GitHub (Sep 17, 2025):

+1 swarm support is the only thing keeping me from moving from Portainer

@acheslow commented on GitHub (Sep 17, 2025): +1 swarm support is the only thing keeping me from moving from Portainer
Author
Owner

@maradanasai commented on GitHub (Oct 22, 2025):

+1 swarm support is the only thing keeping me as well like others, to move from portainer

@maradanasai commented on GitHub (Oct 22, 2025): +1 swarm support is the only thing keeping me as well like others, to move from portainer
Author
Owner

@epoch-philosophy commented on GitHub (Oct 26, 2025):

+1 Docker swarm support would be huge. And would move me over to Komodo. Just adding my voice here too!

@epoch-philosophy commented on GitHub (Oct 26, 2025): +1 Docker swarm support would be huge. And would move me over to Komodo. Just adding my voice here too!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/komodo#19