Open daeho-ro opened 1 week ago
@daeho-ro have you tried docker compose
instead? (see https://docs.docker.com/compose/migrate/)
@dgageot It is, of course working but my question is why it is deleted even if the command is deprecated. I cannot find any statement and just want to know what happen.
@daeho-ro I understand. @glours @ndeloof, was the removal planned? Should it have been listed in the release notes?
+1, running into this issue too 🙏
Same here.
I used to work around this (or rather towards the deprecation) by creating a script /usr/local/bin/docker-compose
simply running
docker compose "$@"
This however is now erroring as well:
Error: spawn Unknown system error -8
Code: Unknown system error -8
Compose v2 can run standalone as docker-compose
and AFAICT this should be the case within Docker Desktop, but maybe recent removal for legacy compose-cli broke this ?
@dgageot there is something wrong in the update process, the symlink should now point to the CLI plugin binary. I'll work with the Stability team to fix this
As a workaround you can run the following command:
sudo ln -sf /Applications/Docker.app/Contents/Resources/cli-plugins/docker-compose /usr/local/bin/docker-compose
While this fixes the problem with running docker-compose
at all, my projects now refuse to start due to undefined networks. Since the networks exist prefixed with the project name (just as before) I assume there's something else going wrong with the cli plugin.
@LikeAJohny please report error running you application on github.com/docker/compose with error details so we can investigate
@ndeloof Did so :+1:
Closed the bug ticket since the error originated from an error on my behalf, sorry!
Getting this too!
As a workaround you can run the following command:
sudo ln -sf /Applications/Docker.app/Contents/Resources/cli-plugins/docker-compose /usr/local/bin/docker-compose
Thank you so much !
Is this really an issue or should we just start using docker compose
instead? And if you like to use the dashed command you can ofc create an alias to this as well.
I'm following along with this question ☝🏻.
Is this really an issue or should we just start using
docker compose
instead? And if you like to use the dashed command you can ofc create an alias to this as well.
We have a bunch of scripts executing docker-compose
in our CI/CD.
And shell aliases (depending on how IT sets it up) are usually only loaded in interactive shells.
Are there plans to fix this? I understand there may be intent for users to migrate to docker compose
, but isn't that a breaking change that should be go in a major version bump (e.g. 5.0.0
)?
Description
When upgrade docker to 4.32.0, there is no
docker-compose
command and I confirmed that the.app
package does not have one.I am not sure if this change is intentional or if it is a side effect of removing
com.docker.cli
. Can anyone confirm this?Reproduce
Expected behavior
No response
docker version
docker info
Diagnostics ID
67E16B9B-A03B-4D9E-8809-F784135F4E3D/20240707071016
Additional Info
No response