Because there is no good way to scope the docker plugins (Using DOCKER_CONFIG could break too many different ways and there isn't a docker compose plugin PATH-like environment variable we can just use, unfortunately), it doesn't seem like a good idea to install a version of docker compose plugin in the user's home directory that will affect everything. So instead we print out a message for the user to do that and it's now on them. Docker compose v2 is a requirement, not something we can easily set up for them.
DOCKER_CONFIGcould break too many different ways and there isn't a docker compose pluginPATH-like environment variable we can just use, unfortunately), it doesn't seem like a good idea to install a version of docker compose plugin in the user's home directory that will affect everything. So instead we print out a message for the user to do that and it's now on them. Docker compose v2 is a requirement, not something we can easily set up for them.