bump docker-compose dependency to avoid dependency hell

[lorenzwalthert]

Describe the feature you'd like

You depend on almost two year old docker-compose version (as an optional dependency). I.e. you depend on 1.29.2, but there is 2.15.1 This old dependency itself has version constraints on other packages such as jsonschema. My project (and/or its dependencies) depend on newer versions of jsonschema and hence I can't resolve the dependencies in my project.

How would this feature be used? Please describe.

Make it easier for users to resolve their dependencies.

Describe alternatives you've considered

Not making docker-compose a requirement in my poetry setup and install ad-hoc with pip install. This may cause unexpected conflicts.

Additional context
The use of docker-compose seems very limited in this repo and hence an upgrade and potential adaption effort would be low.

[j-adamczyk]

+1, this is quite a problem for me, since we are using Docker Compose in modern version across all apps, and I would very much like to avoid using very old 1.X version just for SageMaker projects

[jmahlik]

I believe this was closed by #3913 in version 2.164+. The docker compose plugin is a separate non-python install and need to be aliased to docker-compose via a shim on the users PATH. Something like this.

cat << EOF | sudo tee /usr/local/bin/docker-compose
#!/bin/bash
docker compose --compatibility "\$@"
EOF

[lorenzwalthert]

Right... I won't need the alias, but thanks.