-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Discard "docker-compose" in favor of "docker compose" #222
Comments
Hi there, This report has been escalated for further investigation. If you have more information that can help us, please add it below. Thanks! |
The above issue, #232, is unrelated to this issue. My instance is successfully using the 'docker compose' binary located in $HOME/.docker/cli-plugins
I manually update this file using the Docker Compose Github releases page https://github.com/docker/compose/releases. I do not have the binary that comes with the apt package docker-compose-plugin in my system path so it's not being used.
|
The #232 actually is related. If you manually install "docker-compose", the "bitwarden.sh" script is written to use it by preference. And it's obsolete and unsupported, and should no longer even be attempted in place of the better supported "docker compose" command. |
just adding my experience/pain regarding the use of docker-compose in the bitwarden.sh script 😅
even though it actually does exists. |
Do you need a pull request for this? Because the old 'docker-compose' binary is now six months older. |
The published "docker-compose" binary is obsolete and unmaintained, and the "docker compose" plugin is actively being supported and built into contemporary releases of docker. Please discard the use of "docker-compose" or at least check for and use "docker compose" first in the bitwarden.sh, run.sh, and run.ps1 files. Its use encourages separately installing and relying on obsolete software, which should not be welcomed for security related software.
The text was updated successfully, but these errors were encountered: