Skip to content
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

start.sh uses ‚docker compose‘ instead of ‚docker compose‘ #84

Open
RRFfm opened this issue Oct 7, 2022 · 3 comments
Open

start.sh uses ‚docker compose‘ instead of ‚docker compose‘ #84

RRFfm opened this issue Oct 7, 2022 · 3 comments

Comments

@RRFfm
Copy link

RRFfm commented Oct 7, 2022

I use ‚Compose V2‘ on my device, so ‚docker-compose’ ist not available and the script fails. As a quickfix, I changed all ‚docker-compose‘ to ‚docker compose‘.

@rsplaul
Copy link

rsplaul commented Dec 9, 2023

As a workaround you might as well create an executable file /usr/local/bin/docker-compose on the docker host with the following content:

#!/bin/sh

/usr/bin/docker compose "$@"

@Darth-Carrotpie
Copy link

As a workaround you might as well create an executable file /usr/local/bin/docker-compose on the docker host with the following content:

#!/bin/sh

/usr/bin/docker compose "$@"

After that, if you got permission problems, do this:
sudo chmod +x /usr/local/bin/docker-compose

@Darth-Carrotpie
Copy link

Then if you still have problems with docker permissions, i.e. I had this being thrown:
permission denied while trying to connect to the Docker daemon socket...<....>


Solved it using reply for this SO post

  1. Create the docker group if it does not exist

$ sudo groupadd docker

  1. Add your user to the docker group.

$ sudo usermod -aG docker $USER

  1. Log in to the new docker group (to avoid having to log out / log in again; but if not enough, try to reboot):

$ newgrp docker

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants