Summary: | app-containers/docker-compose:2: docker-compose executable no longer in PATH | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | John Helmert III <ajak> |
Component: | Current packages | Assignee: | William Hubbs <williamh> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | chris |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
John Helmert III
![]() ![]() ![]() ![]() It doesn't belong in the path. It is run as a subcommand of docker, e.g.: docker compose foo instead of: docker-compose foo Let me know if you have any more questions. Thanks, William I still think it is better to just symlink it given how cheap it is and how many workflows you just destroyed by not providing it. docker-compose 2.x is slotted, so it doesn't remove docker-compose 1.x when it is installed, so nothing is destroyed as you said above. If you keep running "docker-compose" you get docker-compose 1.x "docker compose" with a space instead of a "-" gives you docker-compose 2.x. In short, you don't start using docker-compose 2.x unless you change the command you are running. (In reply to William Hubbs from comment #3) > docker-compose 2.x is slotted, so it doesn't remove docker-compose 1.x > when it is installed, so nothing is destroyed as you said above. If you > keep running "docker-compose" you get docker-compose 1.x > "docker compose" with a space instead of a "-" gives you docker-compose 2.x. > > In short, you don't start using docker-compose 2.x unless you change the > command you are running. There are a lot of workflows that are indeed "destroyed", plenty of scripts that just call docker-compose and work with both 2.x and 1.x. *** Bug 866109 has been marked as a duplicate of this bug. *** |