4 ms·
Ditto. For a single machine you don't need "orchestration" - you just need something cleaner than a bash script to start/stop and potentially restart your conta
by seabrookmx 8y ago
Ditto. For a single machine you don't need "orchestration" - you just need something cleaner than a bash script to start/stop and potentially restart your containers.
I set up my home server with minikube more as a learning exercise, but went back to docker-compose for running all the things I actually rely on (Plex for instance) just because it's so much simpler.
- pas 8y agoAgreed. k8s makes no sense on 1 node. But in my experience Swarm is just not enough when you have more than one node. You have to work around a few missing key features. (Like the management of deployments. With Swarm you have stacks, and you can update them, but you can't easily roll back the update, you can't easily manage/configure the update. And if the update gets stuck, it just gets stuck, it's not managed.)
- sandGorgon 8y agoThe stuck issue is not a limitation of Swarm, but was a bug that has gotten fixed in 18.06 - https://github.com/moby/moby/issues/37493 https://github.com/moby/moby/issues/37493 Rollback has existed for a while now - https://docs.docker.com/engine/reference/commandline/service_rollback/ https://docs.docker.com/engine/reference/commandline/service... . you can actually tune the parallelism and the delay