I've been using `docker-compose` (with a hyphen) in my project, but I see that the newer Docker documentation often references `docker compose` (without the hyphen, as a subcommand). I'm curious about the actual differences between these two commands. Is `docker-compose` on its way out? Should I update my project to use `docker compose` instead? Are there any breaking changes or compatibility issues I need to be aware of if I make the switch? Also, what's the best migration path if I decide to upgrade? My setup works fine with `docker-compose`, but I want to ensure I'm up to date with best practices and not using any outdated tools. Any insights would be really helpful! Thanks!
3 Answers
Yeah, `docker-compose` is the old Python version, and with `docker compose`, you get a more integrated experience. Stay updated by adopting the newer command for a better toolset!
Upgrading to `docker compose` is a good move! Even better, it creates an alias so you can continue using `docker-compose` if necessary. This way, you won't lose any functionality while transitioning to the newer command.
Just a heads up, `docker compose` is not only newer but also more powerful. It follows the official compose spec. Don't forget to check out Docker's migration guide for compatibility and steps to ensure a smooth transition!
That sounds neat! Can the new binary still work with podman?