Arch Linux

Can confirm happened to me as well, rolling back to 1.29.2-1 fixes immediately.

With 2.0.0-1, "which docker-compose" returns "which: no docker-compose in (/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl)"

Happens to me. Tried reinstalling - no success. Full output below:

--- BEGIN OUTPUT ---
13:06 ~ sudo pacman -S docker-compose
warning: docker-compose-2.0.0-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) docker-compose-2.0.0-1

Total Installed Size: 29,89 MiB
Net Upgrade Size: 0,00 MiB

:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring [#######################################################] 100%
(1/1) checking package integrity [#######################################################] 100%
(1/1) loading package files [#######################################################] 100%
(1/1) checking for file conflicts [#######################################################] 100%
(1/1) checking available disk space [#######################################################] 100%
:: Processing package changes...
(1/1) reinstalling docker-compose [#######################################################] 100%
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
13:06 ~ docker-compose
zsh: command not found: docker-compose
13:06 ~ sudo pacman -Ql docker-compose
docker-compose /usr/
docker-compose /usr/lib/
docker-compose /usr/lib/docker/
docker-compose /usr/lib/docker/cli-plugins/
docker-compose /usr/lib/docker/cli-plugins/docker-compose
docker-compose /usr/share/
docker-compose /usr/share/licenses/
docker-compose /usr/share/licenses/docker-compose/
docker-compose /usr/share/licenses/docker-compose/LICENSE

--- END OUTPUT ---


Reinstalled from AUR - there are executables in /usr/bin, and some other differences as well.

And yeah, there is no docker-compose v2 at the moment - last version is 1.29.2 https://docs.docker.com/compose/release-notes/
So this 2.0.0 is apparently a reference to some other thing.

A reply to my post on reddit suggests that compose has now been integrated into docker as a plugin so the command is now docker compose (no hyphen).

I've not seen any announcements on this so in the process of trying to confirm.

I would have expected this change to be announced on the arch mailing list at least?

https://github.com/docker/compose/issues/8697

@Neil Parton

> A reply to my post on reddit suggests that compose has now been integrated into docker as a plugin so the command is now docker compose (no hyphen).

This is something I checked as well - inferring from the `pacman -Ql` output that it would have become a docker plugin. But:

--- BEGIN OUTPUT
$ docker compose
docker: 'compose' is not a docker command.
See 'docker --help'
--- END OUTPUT

I guess the docker package should receive an update as well?

And for sure, it would be a great idea to add a `docker-compose` shell script with e.g.
```
#!/bin/sh
$ECHO "Please be aware that the new recommended way is to use 'docker compose' instead.
$SHELL docker compose $@
```
(I sincerely hope it was just a mistake that accidentally got released too early. Otherwise, it looks like an "I don't care about the users" type of thing...)

So for now, the simplest obvious fix is to use the docker-compose version from AUR.

I agree, I've rolled back and will probably stay there for a little while. I also agree that if docker-compose has been rolled in to docker then we would have expected both the docker package to have been upgraded at the same time and an announcement made to the mailing list and all the other appropriate places as this is a breaking change.

@Neil Parton
Thank you so much!