NAS-Synology DS218 - Run docker / Portainer / PIHOLE Server

Tested on my DS218.

Pain point I try to solve

NAS Synology DS218 is using a aarch64 architecture that doesnt support official docker synology package. Trying to bypass that by install aarch64 docker binaries using direct ssh connection to the NAS.

Most of the data is coming from https://gist.github.com/ta264 and https://wiki.servarr.com/docker-arm-synology I did my own repo to handle versionning and review the code/script myself.

To help understand what is done you can also read this : https://dev.to/behainguyen/synology-ds218-unsupported-docker-installation-and-usage-2g1n

Activate ssh on your NAS and get root

1. On your DSM interface go to the parameters / Terminal & SNMP
2. Check activate ssh access box

3. Open a powershell terminal and run this commands:

ssh user@yourNasIP -p 22

type yes

type your password

to get root :

sudo -i

Expected outcome :

Installation of docker and configuration

curl https://raw.githubusercontent.com/griai/NAS-Synology/main/get-docker.sh | sh

If all goes well you should see the message:

Done. Please add your user to the Docker group in the Synology GUI and reboot your NAS.

Add your user to docker group in DSM interface

Reboot your NAS

Build a portainer container

cd /volume1/@docker/portainer
docker-compose up -d

Expected outcome :

Then go to the portainer homepage to configure it :

in your browser : youNasIP:9000

Setup your admin account

Portainer is now working and should ask to setup the admin password:

Build a pihle container

Now if you want to build pihole image and start a container:

cd /volume1/@docker/portainer
docker-compose up -d

expected outcome :

You can now access your pihole homepage using YourNasIP:8080/admin url

Build a snikket container

(from snikket.org/service/quickstart)

For running a snikket server you first need to have a domain name that is reachable via DNS and that you can create subdomains on. Snikket provides a built-in web server that must be reachable on port 80. We assume that you are not running any existing websites on the same server. Also make sure that the relevant ports are forwarded if you are behind a router or firewall.

As a last step you have to enter some configuration data in the file snikket/snikket.conf.

Afterwards, you can simply

cd /volume1/@docker/snikket
docker-compose up -d

Update containers

In order to update the docker containers using docker-compose, run

docker-compose pull
docker-compose up --force-recreate --build -d
docker image prune -f

from the respective directories.