-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docker-compose docker: 'compose' is not a docker command#6569
Comments
Having the same issue here :( |
Same issue here. macos 12.6.1 m1. docker 4.14.0
|
Definitely something wrong with the latest release. I've downgraded to 4.13.1 and compose is working again. |
I can confirm that 4.13.1 is working for me as well. The issue appears on version 4.14.0 only. |
docker-compose works for me if I switch off "Use docker compose v2". on 4.14.0 |
Can confirm this worked for me (M1 pro macbook on Ventura 13.0.1). Installing 4.13.1 didn't work for some reason (fresh install) |
This does not do the trick for me, and neither does downgrading to On macOS Ventura 13.0 (Intel) |
Thanks for reporting. Sadly, I wasn't able to reproduce this issue on 4.14.0. Can somebody experiencing this issue upload a diagnostic, as documented here: https://docs.docker.com/desktop/troubleshoot/overview/#diagnose |
hello guys, I was also getting the same error here, but I managed to get around it using the docker-compose-v1 command
|
Can you check contents of |
I don't have this folder here running the command: |
Do you get the same error for |
yes i get the same error running these commands. |
Which version did you update from, or was this from a fresh install? It's possible this is a consequence of updating from 4.13.1 to 4.14, would be good to narrow that down if anyone is seeing this error from updating from an older version than 4.13.1. |
i have it too. It's a fresh install not an update / upgrade |
i just installed docker desktop
|
Great, thanks for quick feedback. I'm guessing theres likely an error in the installation log. If you can upload a diagnostic that'd be great. Sorry for the inconvenience. |
I'm sorry but I don't have the installation log. what I can say is that I downloaded the latest version available from the website |
Output of /Applications/Docker.app/Contents/MacOS/com.docker.diagnose check
|
Yea turning off docker compose v2 worked for me. Any idea what the new v2 compose does? |
Looks like the fault could be a missing symlink between Can you try manually creating this:
The commands may need to be run with sudo if /usr/local is owned by root. |
I was experiencing the same issue. The commands @mikeparker suggested fixed the issue. Thank you very much! |
The commands @mikeparker shared fixed the issue for me as well. ❤️ |
Same issue here with MacBook Pro M1 Pro with Ventura 13.0.1. The commands @mikeparker suggested fixed the issue. Thanks a lot. |
The commands fixed it for me as well |
The commands fix the issue without having to turning off the docker compose v2 checkbox. Thanks @mikeparker! |
check |
Also works for me, thanks! |
Works for me as well, thanks. |
Thanks a lot, @mikeparker. Have been struggling with it for two days. |
Thanks @mikeparker! Crazy that this is needed when installing Docker Desktop on a fresh MBP. |
The solution by @mikeparker worked for me as well. Nicely done. |
Looks like Docker Desktop 4.14.1 (91661) fixed it for me |
We've now released 4.14.1 with the fix. Thanks everyone for helping track it down. Closing! |
still not fixed for me (after installing 4.14.1). was working 48 hours ago. broke |
I updated my docker app to 4.14.1 (91661) and only after that issue is gone |
Confirm 4.14.1 is good. |
@mikeparker This is not fixed. Not only that, docker compose is now busted as well. /Applications/Docker.app/Contents/MacOS/com.docker.diagnose check Starting diagnostics [PASS] DD0027: is there available disk space on the host? [PASS] DD0028: is there available VM disk space? [PASS] DD0018: does the host support virtualization? [PASS] DD0001: is the application running? [PASS] DD0017: can a VM be started? [PASS] DD0016: is the LinuxKit VM running? [PASS] DD0011: are the LinuxKit services running? [PASS] DD0004: is the Docker engine running? [PASS] DD0015: are the binary symlinks installed? [PASS] DD0031: does the Docker API work? [PASS] DD0013: is the $PATH ok? [PASS] DD0003: is the Docker CLI working? [PASS] DD0014: are the backend processes running? [PASS] DD0007: is the backend responding? [PASS] DD0008: is the native API responding? [PASS] DD0009: is the vpnkit API responding? [PASS] DD0010: is the Docker API proxy responding? [PASS] DD0012: is the VM networking working? [SKIP] DD0030: is the image access management authorized? [PASS] DD0019: is the com.docker.vmnetd process responding? [PASS] DD0033: does the host have Internet access? [PASS] DD0018: does the host support virtualization? [PASS] DD0001: is the application running? [PASS] DD0017: can a VM be started? [PASS] DD0016: is the LinuxKit VM running? [PASS] DD0011: are the LinuxKit services running? [PASS] DD0004: is the Docker engine running? [PASS] DD0015: are the binary symlinks installed? [PASS] DD0031: does the Docker API work? [PASS] DD0032: do Docker networks overlap with host IPs? No fatal errors detected. ~ % docker compose docker: 'compose' is not a docker command. See 'docker --help' ~ % which docker /usr/local/bin/docker ~ % ls -altr /usr/local/bin/docker lrwxr-xr-x 1 dmclau admin 54 Nov 24 22:52 /usr/local/bin/docker -> /Applications/Docker.app/Contents/Resources/bin/docker ~ % docker compose docker: 'compose' is not a docker command. See 'docker --help' ~ % /Applications/Docker.app/Contents/Resources/bin/docker -v Docker version 20.10.21, build baeda1f ~ % /Applications/Docker.app/Contents/Resources/bin/docker compose -f unknown shorthand flag: 'f' in -f It is clearly busted, and I just uninstalled and reinstalled it. I still had to manually create all of the symlinks to /usr/local/bin because Docker Desktop is not doing it like it use to in the past. I manually had to create all of these symlinks or the diagnotics would fail... lrwxr-xr-x 1 dmclau admin 54 Nov 24 22:52 docker -> /Applications/Docker.app/Contents/Resources/bin/docker lrwxr-xr-x 1 dmclau admin 62 Nov 24 22:53 com.docker.cli -> /Applications/Docker.app/Contents/Resources/bin/com.docker.cli lrwxr-xr-x 1 dmclau admin 62 Nov 24 22:54 docker-compose -> /Applications/Docker.app/Contents/Resources/bin/docker-compose lrwxr-xr-x 1 dmclau admin 80 Nov 24 22:55 docker-compose-v1 -> /Applications/Docker.app/Contents/Resources/bin/docker-compose-v1/docker-compose lrwxr-xr-x 1 dmclau admin 60 Nov 24 22:56 docker-index -> /Applications/Docker.app/Contents/Resources/bin/docker-index lrwxr-xr-x 1 dmclau admin 73 Nov 24 22:56 docker-credential-desktop -> /Applications/Docker.app/Contents/Resources/bin/docker-credential-desktop lrwxr-xr-x 1 dmclau admin 77 Nov 24 22:57 docker-credential-osxkeychain -> /Applications/Docker.app/Contents/Resources/bin/docker-credential-osxkeychain lrwxr-xr-x 1 dmclau admin 75 Nov 24 22:58 docker-credential-ecr-login -> /Applications/Docker.app/Contents/Resources/bin/docker-credential-ecr-login lrwxr-xr-x 1 dmclau admin 55 Nov 24 23:00 kubectl.docker -> /Applications/Docker.app/Contents/Resources/bin/kubectl I think the reason that the symlinks aren't getting created is because the docker install command is busted. /Applications/Docker.app/Contents/MacOS/install config Error: accepts 1 arg(s), received 0 |
I was able to get docker compose working by doing the following... mkdir -p /usr/local/lib/docker You guys have got to figure out the Docker install problems on Mac OS. This has been going on for over 6 months now, it seems like every time there is a patch to MacOS I end up spending days trying to get Docker working again. The symlink issue has been an issue for some time now, and it's everyone on my team that is having the issues, as well as hundreds of hits on the google searches. This is a real problem and it needs to be investigated and fixed. If I can manually create all the symlinks with my user, then so should the Docker install command, and it doesn't. If you want to send me a debug build I'd be happy to run it to tell you why it's silently failing. |
@danshome if you’re still having problems with the symlinks after updating to 1.14.1, could you create a new issue? |
Facing this issue with 4.15.0. |
FWIW - I had this issue after moving to a new M1 Macbook. I had a corrupted /usr/local/lib/docker/cli-plugins directory. After deleting that and the stuff in usr/local/bin, I reinstalled Docker and |
With M1 mac mini I installed docker to an external ssd, and did set the disk image location to the same external ssd. After I faced this error, I installed the latest update (4.15.0), restarted the operating system, and the error went away. |
same, Poor testing |
this with sudo works for me |
I use a Macbook Air (M1 chip) and the docker compose didn't work for me in the latest version of docker (4.16.2), so I downgraded to the v4.13.1, toggled the “Use Docker Compose V2” in the general tab, and ran "docker-compose-v1 build --force-rm" in the terminal . It finally worked |
Closed issues are locked after 30 days of inactivity. If you have found a problem that seems similar to this, please open a new issue. /lifecycle locked |
Expected behavior
Expected to be able to run compose.
Actual behavior
compose seems to load docker and docker cannot find compose.
Information
Output of
/Applications/Docker.app/Contents/MacOS/com.docker.diagnose check
Steps to reproduce the behavior
docker-compose
. getthe
docker
command seems to work but it cannot find the docker-compose commandI have these under bin
running the compose command directly
The text was updated successfully, but these errors were encountered: