In short, is docker-compose dead or will be dead forever in near to mid term future? And lastly, what is the current state of affairs?
In short, is docker-compose dead or will be dead forever in near to mid term future? And lastly, what is the current state of affairs?
9 comments
I prefer to run DBs using docker and docker-compose on my homeLab linux servers than installing MySQL through the package manager. A lot cleaner/easier/faster to configure.
It's so easy and simple, I don't know how I ever lived without it. So much is supported, I feel like it's so easy to get everyone on a team on the same page without having to install and configure so many different things.
Funny enough, despite all of these containers, I actually don't deploy any to actually run any of the code or dependecies. It's all just for the ease and speed of development.
Podman, which is a docker alternative also refuses to support docker-compose and points users towards kubernetes yaml.
From their repo:
"We believe that Kubernetes is the defacto standard for composing Pods and for orchestrating containers, making Kubernetes YAML a defacto standard file format. Hence, Podman allows the creation and execution of Pods from a Kubernetes YAML file (see podman-play-kube). Podman can also generate Kubernetes YAML based on a container or Pod (see podman-generate-kube), which allows for an easy transition from a local development environment to a production Kubernetes cluster."
On the other hand, docker-compose is now a proper spec instead of a docker only tool which may prolong its life
https://compose-spec.io/
For the flaws of Docker, local development is just easy - which is really nice. It concerns me to hear that docker-compose might be dead.