4 ms·

> Which got eaten by other orchestration technologies there? Exactly , Kubernetes wants to remove Docker , and the Docker orchestration layer « Docker Compose

by asien 5y ago

> Which got eaten by other orchestration technologies there? Exactly , Kubernetes wants to remove Docker , and the Docker orchestration layer « Docker Compose » is completely dead. Again the founder has left the company with millions , there is no leadership whatsoever it’s a just a zombie company losing millions every year until it’ll declare bankruptcy. Google / Redhat are very well aware of that that’s why they are trying to decouple their product ( Kubernetes/ Openshift ) from docker before it officially become deprecated . [0]https://acloudguru.com/blog/engineering/kubernetes-is-deprecating-docker-what-you-need-to-know https://acloudguru.com/blog/engineering/kubernetes-is-deprec...

0xEFF 5y ago
Kubernetes is already fully decoupled from docker. Defaults for new clusters are containerd today.
jen20 5y ago
> until it’ll declare bankruptcy Or get acquired in a fire sale.
jayd16 5y ago
Docker compose still seems like the easiest solution for a quick local dev env, no? Is there an easier turnkey solution for users? (I don't care about the setup as much as the ease of use by devs who didn't set it up.)
- thorum 5y ago
  skaffold and minikube (which runs a simple Kubernetes cluster on your local dev computer) are great - the developer just types “skaffold dev” in their terminal and skaffold handles the entire process of building and deploying code into minikube, with instant live updates whenever files change. https://skaffold.dev/ https://skaffold.dev/ https://minikube.sigs.k8s.io/docs/ https://minikube.sigs.k8s.io/docs/
  - jayd16 5y ago
    Still seems more complex than docker compose even if the file watching is nice. I'll look into it some more though, thanks.
- JeremyNT 5y ago
  Docker compose is still really good for the use case that you want to lump a bunch of services together and go. It's great for local development and it's just fine for deploying a set of services to a single host. The "issues" with compose are 1) it doesn't make Docker any money, thus doesn't see much in the way of enhancements, and 2) it doesn't even try to do the enterprisey things that Kubernetes does. Also, you can drop podman-compose in and run most docker-compose files with no or minimal modifications, so it's not like docker-compose itself is even unique.

by asien 5y ago

0xEFF 5y ago

Kubernetes is already fully decoupled from docker. Defaults for new clusters are containerd today.

jen20 5y ago

> until it’ll declare bankruptcy Or get acquired in a fire sale.

jayd16 5y ago

Docker compose still seems like the easiest solution for a quick local dev env, no? Is there an easier turnkey solution for users? (I don't care about the setup as much as the ease of use by devs who didn't set it up.)

thorum 5y ago
skaffold and minikube (which runs a simple Kubernetes cluster on your local dev computer) are great - the developer just types “skaffold dev” in their terminal and skaffold handles the entire process of building and deploying code into minikube, with instant live updates whenever files change. https://skaffold.dev/ https://skaffold.dev/ https://minikube.sigs.k8s.io/docs/ https://minikube.sigs.k8s.io/docs/
- jayd16 5y ago
  Still seems more complex than docker compose even if the file watching is nice. I'll look into it some more though, thanks.
JeremyNT 5y ago
Docker compose is still really good for the use case that you want to lump a bunch of services together and go. It's great for local development and it's just fine for deploying a set of services to a single host. The "issues" with compose are 1) it doesn't make Docker any money, thus doesn't see much in the way of enhancements, and 2) it doesn't even try to do the enterprisey things that Kubernetes does. Also, you can drop podman-compose in and run most docker-compose files with no or minimal modifications, so it's not like docker-compose itself is even unique.