Setup script fails on Synology NAS with error: "id: ‘docker’: no such user"

[southnyarra]

Hey there - just tried following the readme to get this up and running on my Synology DS723+.

Environment

• Device: Synology NAS DS723+
• Operating System: DSM 7.2.2-72806 Update 4
• Docker Version: Container Manager 24.0.2-1543

Problem Description

When running the setup script, the installation fails with the following error:
🚀 Starting environment setup for your Synology Bitcoin Full Node stack
id: ‘docker’: no such user

What I've Tried

I have attempted the following solutions without success:

1. Running as a standard user with PUID/PGID:

   PUID=$(id -u) PGID=$(id -g) curl -sSL [https://raw.githubusercontent.com/magicdude4eva/btc-fullnode-stack/main/setup.sh](https://raw.githubusercontent.com/magicdude4eva/btc-fullnode-stack/main/setup.sh) | bash

   This resulted in the same error.

2. Running as the root user:

   sudo -i
   curl -sSL [https://raw.githubusercontent.com/magicdude4eva/btc-fullnode-stack/main/setup.sh](https://raw.githubusercontent.com/magicdude4eva/btc-fullnode-stack/main/setup.sh) | bash

   This also resulted in the same "no such user" error.

It seems the script has a hard dependency on a 'docker' user that does not exist in a standard Synology environment. Could you please advise on a workaround or an update to the script to support Synology NAS installation?

Thank you!

[southnyarra]

Just thought I'd offer an update on some testing I've done.

The issues all boil down to the setup script assuming there's a user called docker, which isn't automatically created when Container Manager is installed on the Synology NAS.

I manually hardcoded the uid and gid of my administrator account into the script to get it to work.

It then had flow on effects for folder permissions both in the setup script and the docker-compose.yml file, so the uid and gid had to be manually specified in there. Finally, Synology then doesn't respect permissions set through SSH, so I had to manually set administrator read/write permissions for the volume 1 and volume 2 folders.

The node is currently syncing, so will see how it goes.

[Fexik]

I have the same problem...

[southnyarra]

I have the same problem...

FYI - I ended up having further issues after fixing that last step and wasting many more hours on trying to get it worked and abandoned this. I also discovered the creator's personal BTC address was in the config file for CKPool. While some people would know to update that to pay out any solved blocks, I suspect many wouldn't.

A solution that I'm now using that works fine is running Umbrel OS through Portainer and Docker. It then happily runs both the Bitcoin Core node and also Public Pool for miners.

[Fexik]

I am used UmbrelOS, everything started up on the first try, both the node and the public pool
https://hub.docker.com/r/dockurr/umbrel