Support new docker cli which contains docker-compose replacement
See original GitHub issueDescription of the new feature/enhancement
docker-compose has been rewritten in Go and made a part of the docker cli. The rewritten docker compose command (now part of the docker cli and no longer a standalone app) interacts better with shells and such. See: https://github.com/docker/roadmap/issues/15
The new docker compose command also includes new command options that are not going to be backported to docker-compose cli. Docker desktop has migrated to the new docker cli which contains docker compose, because of this I have rewritten startup scripts to use docker compose
instead of docker-compose
. Those scripts don’t work with container-desktop currently.
Proposed technical implementation details (optional)
No response
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Migrate to Compose V2
The easiest and recommended way is to make sure you have the latest version of Docker Desktop, which bundles the Docker Engine and...
Read more >Announcing Compose V2 General Availability
Docker Compose V2 is a drop-in replacement for Compose V1. In most cases, you can remove the dash or enable aliasing of docker-compose...
Read more >Overview of docker compose CLI
The new Compose V2, which supports the compose command as part of the Docker CLI, is now available. Compose V2 integrates compose functions...
Read more >Compose file versions and upgrading
The latest and recommended version of Compose is the Compose Specification. Make sure you switch to Compose V2 with the docker compose CLI...
Read more >Install the Compose plugin
Download and install Docker Compose on Linux with this step-by-step handbook. This plugin can be installed manually or by using a repository.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@rouke-broersma could you create a new issue for this ?
I am also seeing some other errors. I don’t know if they are related, should I create a new issue?:
I’m getting this result every time I run
docker-compose up -d
from a fresh boot. First it errors withdocker-proxy
cannot be found exactly once, and every subsequentdocker-compose up
errors with port is already allocated.This is from a fresh boot where docker-desktop has not been started and where I have deleted all docker-desktop wsl distros. Netstat does not show port 8080 as being bound by anything in windows or in my WSL distro.
When then killing container-desktop and starting docker-desktop the port binding of that container works fine.