start.sh uses ‚docker compose‘ instead of ‚docker compose‘
RRFfm opened this issue · comments
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‘.
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 "$@"
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
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
- Create the docker group if it does not exist
$ sudo groupadd docker
- Add your user to the docker group.
$ sudo usermod -aG docker $USER
- 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