Sadly like many Docker Swarm based projects, this has become abandonware. I use Docker Swarm with Portainer for managing services with ecoeats[1], a decision that was made years ago, just before Swarm was revealed to be absolutely dead in the water. I initially used Swarmlet before switching to Portainer, as there were far too many bugs and missing tools needed to effectively manage a Swarm that went beyond stateless Node containers.
With Portainer and Swarm I've been forced to manually intervene with rollouts more times than I would have liked due to Swarm-specific errors and other quirky networking behaviour. At least it's simpler than Kubernetes!
I really liked the option to deploy through a git push without additional setup. But it indeed looks like abandonware, thanks for sharing your experience! If you would start over, would you choose for Portainer and Swarm again? Do you know of any alternatives to Swarmlet?
Swarm was great. Docker/Moby should never have abandoned it.
Kubernetes solves a similar class of problems to Swarm, but in a much more complex way. Sometimes that complexity helps solve problems. For many organizations, though, Swarm would have been the better option.
Both Swarm and Kubernetes have their purposes. I'm sad that no option has popped up to replace Swarm in the "simple and easy container orchestration" space. Now it's either Kubernetes or... ECS, I guess.
I've been trying out Nomad on a home server setup, its still not as simple as Swarm and has some hard edges to learn around, but overall it hasn't been a bad experience, definitely easier than my attempts at k8s. And Nomad got basic built in service discovery in the last couple versions, which was the main thing turning me away (it used to require running Consul).
Docker should have built a "better" K8s distro. Right now what they have is junk. Even Rancher isn't filling the niche. I don't think K8s is such a huge hill for new folks. Anyone who spends 5 minutes looking at basic deployment YAML can figure out what to do next. Getting a cluster up and running is the hardest part these days. Minikube, K8s in Docker, and even K3s all suck. There is still ample opportunity for them to own this market.
I really like the option to deploy through a git push without additional setup, and I am looking for something similar to host a bunch of containers. Does anyone here have experience with such a tool, and what is your experience regarding reliability?
It's great if you want to run generic utilities at home (though I've used it at work in internal production and it was good), but it doesn't do ingress, so you have to bring your own.
It's basically a fancy/opinionated wrapper over "git pull && docker-compose up", with allowing you to specify all configuration in one file/repo.
A 2nd for Dokku. It's dead simple and works on any host. Yes, it is limited to single server architecture, but for most people this shouldn't be a problem. Vertical scaling can go a long way.
I have built all our infrastructure on Docker Swarm before learning about its state. Currently waging migrating to Nomad out of fear for K8s complexity - I’ve worked with it in a previous job with more employees than now, and it still was a big hassle - but am afraid I’ll repeat the same mistake and should just bite the bullet.
- Single-server and non-secure (no mTLS; no ACLs) clusters are super easy to set up and a great way to try out things before committing.
- ...However, enabling especially ACLs but also TLS on running clusters is going to be more hassle than simply setting up a fresh, properly bootstrapped cluster.
- Their minimum and recommended resource requirements are hugely inflated, you can generally get good mileage out of way less
- ...However: Do follow their advice on keeping nodes single-responsibility (ie don't run a consul server and nomad server on the same node; generally keep your servers dedicated and not running jobs)
- Consul and Vault integrations are generally rock solid.
- ...However: Nomad native service discovery is not yet (wrt consistency and template rewrites). Consul Connect may or may not have edge (it's some time since last we seriously tried it).
- learn.hashicorp.com has material for most things you want to do.
- Put all your ACL configuration in Terraform (or whatever else you have for the same purpose)
Best to stay the hell away from k8s if you care about being productive. You're not Google and we'll all be better for it when everyone admits that fact.
[+] [-] lordpankake|3 years ago|reply
With Portainer and Swarm I've been forced to manually intervene with rollouts more times than I would have liked due to Swarm-specific errors and other quirky networking behaviour. At least it's simpler than Kubernetes!
[1] https://ecoeats.uk
[+] [-] mono-bob|3 years ago|reply
[+] [-] the_common_man|3 years ago|reply
[+] [-] bovermyer|3 years ago|reply
Kubernetes solves a similar class of problems to Swarm, but in a much more complex way. Sometimes that complexity helps solve problems. For many organizations, though, Swarm would have been the better option.
Both Swarm and Kubernetes have their purposes. I'm sad that no option has popped up to replace Swarm in the "simple and easy container orchestration" space. Now it's either Kubernetes or... ECS, I guess.
[+] [-] ungawatkt|3 years ago|reply
[+] [-] schoolornot|3 years ago|reply
[+] [-] 131hn|3 years ago|reply
[+] [-] kakoni|3 years ago|reply
Or are you talking about swarm the product (versus docker swarm mode)
[+] [-] mono-bob|3 years ago|reply
[+] [-] daslicious|3 years ago|reply
[+] [-] stavros|3 years ago|reply
https://pypi.org/project/docker-harbormaster
It's great if you want to run generic utilities at home (though I've used it at work in internal production and it was good), but it doesn't do ingress, so you have to bring your own.
It's basically a fancy/opinionated wrapper over "git pull && docker-compose up", with allowing you to specify all configuration in one file/repo.
[+] [-] pgm8705|3 years ago|reply
[+] [-] tough|3 years ago|reply
[+] [-] zainhoda|3 years ago|reply
[+] [-] hummus_bae|3 years ago|reply
[+] [-] 9dev|3 years ago|reply
Does anyone have suggestions?
[+] [-] 3np|3 years ago|reply
- Single-server and non-secure (no mTLS; no ACLs) clusters are super easy to set up and a great way to try out things before committing.
- ...However, enabling especially ACLs but also TLS on running clusters is going to be more hassle than simply setting up a fresh, properly bootstrapped cluster.
- Their minimum and recommended resource requirements are hugely inflated, you can generally get good mileage out of way less
- ...However: Do follow their advice on keeping nodes single-responsibility (ie don't run a consul server and nomad server on the same node; generally keep your servers dedicated and not running jobs)
- Consul and Vault integrations are generally rock solid.
- ...However: Nomad native service discovery is not yet (wrt consistency and template rewrites). Consul Connect may or may not have edge (it's some time since last we seriously tried it).
- learn.hashicorp.com has material for most things you want to do.
- Put all your ACL configuration in Terraform (or whatever else you have for the same purpose)
[+] [-] e12e|3 years ago|reply
[+] [-] whalesalad|3 years ago|reply
[+] [-] kodah|3 years ago|reply
[+] [-] tommica|3 years ago|reply
[+] [-] gigatexal|3 years ago|reply
[+] [-] GiorgioG|3 years ago|reply