You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
update-alternatives doesn't exist on every distro #10
I appreciate that this tool exists, but upate-alternatives / alternatives hardly exists everywhere (e.g. coreos, flatcar, etc...). It would be helpful if you could provide quickstart instructions on how to use the tool such a scenario.
This way people won't just version lock themselves to the latest v1 binary when they realize all their automations based on docker-compose are broken.
This script will just call docker compose. And docker compose is supposed to find Compose V2 because the latter is placed in cli-plugins dir somewhere under /usr, I forgot exact location.
Activity
ndeloof commentedon Oct 3, 2021
Sure, then just setup your PATH to pick up compose-switch before legacy docker-compose V1.
ericb-summit commentedon Oct 5, 2021
Can I call this wrapper simply
docker-composeand put it in the path normally? In that case, how would this script find the real compose v2 binary?slonopotamus commentedon Oct 5, 2021
This script will just call
docker compose. Anddocker composeis supposed to find Compose V2 because the latter is placed incli-pluginsdir somewhere under /usr, I forgot exact location.ndeloof commentedon Oct 6, 2021
Compose V2 binary 2.0.1 actually includes some of the logic from this repo and can be used directly as
docker-composebinary in your pathTitus-von-Koeller commentedon Dec 22, 2021
Cool, that really solved it for us. In Alpine, we did the following:
Thx @ndeloof
slonopotamus commentedon Jan 5, 2022
So... What is the recommended approach?
a. Use Docker Compose V2 as
docker-composeb. Use compose-switch as
docker-compose