2 ms·
It greatly frustrates me that Docker Swarm fell out of favour leaving a void between single-host Docker and Kubernetes. It makes self hosting docker with a smal
by simonjgreen 3y ago
It greatly frustrates me that Docker Swarm fell out of favour leaving a void between single-host Docker and Kubernetes. It makes self hosting docker with a small amount of resilience and orchestration much more challenging.
- mieubrisse 3y agoAgreed, and we're actually trying to bridge this gap at our company Kurtosis! Docker is great for doing dev - fine-grained control over the container, strong predictability guarantees, fast, and relatively lightweight (in comparison with Kubernetes), but you can't run Prod on it unless you start rebuilding Kubernetes primitives like Services from scratch. Our approach has been "build an abstraction over Docker and Kubernetes that can provide the predictability of Docker when you need it (Dev & Test), and the scalability and resilience of k8s when you need it (Prod)", and then handle compiling down to actual Docker & Kubernetes commands. The goal is for the user to have a single environment definition all the way from Dev to Prod, so you don't have to do the dance of "Docker Compose for Dev, Bash on top of Compose for test, and Helm for Prod" (basically this: https://docs.kurtosis.com/assets/images/kurtosis-utility-66539320d2102bbd5e788e65c1d1e89b.png https://docs.kurtosis.com/assets/images/kurtosis-utility-665... )
- Alifatisk 3y agoIs Docker swarms easily reproducable? If so, how?