[Suggestion] Docker-Compose in a Container for Synology ARM devices causes bugs -> use the official latest version! #402
Description
I followed your very convenient guide for Installing Docker on a Synology ARM NAS (thanks!) but I think things could be improved a little bit.
For starters, the script downloads an older version of Docker, so I had to manually edit it to point to the latest version.
But more importantly, it seems to set up Compose via LinuxServer's docker compose container, but this installs a very old version of compose (v1.29.2) and leads to some very strange bugs.
For instance, when supplied with the -f flag to specify a compose file, it always fails to find that file, even if it exists on the system; instead you have to cd into the same directory as the file and run compose without the -f flag. Same thing happens with secrets files defined within the compose file.
I think the better alternative is just to alter the script to follow the official manual installation process for Compose, obviously targeting the aarch64 binary:
DOCKER_CONFIG=${DOCKER_CONFIG:-$HOME/.docker}
mkdir -p $DOCKER_CONFIG/cli-plugins
curl -SL https://github.com/docker/compose/releases/download/v2.34.0/docker-compose-linux-aarch64 -o $DOCKER_CONFIG/cli-plugins/docker-compose
chmod +x $DOCKER_CONFIG/cli-plugins/docker-compose
This is super simple compared to the current installation process, installs the latest version of Compose (v2.34 at time of writing), and resolves all the odd bugs with the containerized version of compose. You could also point people to just manually installing ctop as a lightweight TUI alternative to the clunkier Portainer. The guide is great and made getting docker up and running a breeze, so I really do thank you for it, hopefully these suggestions can improve things for users going forward.