Install “Portainer” on Synology NAS

Source: mariushosting.com

1. Go to “Package Center”, search for “Container Manager” and “Install”. Use the default subnet.
2. Go to “File Station”, open the folder “docker”, and create a new folder “portainer”.
3. Go to Control Panel / Task Scheduler / Create / Scheduled Task / User-defined script and create a new “User-defined script”
4. Fill the “Create task” window with the following values:
   • General: In the Task field type in “Install Portainer“. Uncheck the “Enabled” option. Select root User.
   • Schedule: Select Run on the following date then select “Do not repeat“.
   • Task Settings: Check “Send run details by email“, add your email, then copy paste the code below in the Run command area.
   • docker run -d --name=portainer \ -p 8000:8000 \ -p 9000:9000 \ -v /var/run/docker.sock:/var/run/docker.sock \ -v /volume1/docker/portainer:/data \ --restart=always \ portainer/portainer-ce
   • After that, click OK.
5. Confirm the “Warning” and enter your password. Now “Run” the task.
6. Open the Container Manager on your NAS. On the left sidebar, click Container. Select your portainer container. Click the Details tab.
7. Click the Log tab. In the log, identify the line admin initialization and backup. Click on that line. Perform Ctrl+C on the line and Ctrl-V in the Text Editor.
8. The installation process can take up to a few seconds/minutes depending on your Internet speed connection. Open your browser and type in http://Synology-ip-address:9000. Choose a Username and a strong Password, confirm the password, then paste your setup_token that you have previously copied into the Text Editor. Click Create user.
9. Click Get Started (proceed using the local environment in which Portainer is running in).
10. On the right in the Environments are, click on the little pencil icon (“Edit“).
11. After you click on the little pencil icon, a new page will open. On the Public IP area, type in your own NAS Local IP which, in my case, is 192.168.1.131 then click Update environment.
12. Click Live connect. On the left Portainer sidebar, click on Registries.
13. Click +Add registry then Custom registry. In the Name field area type in Github and in the Registry URL area type in ghcr.io. Click Add registry to save the settings. (Note: The ghcr.io registry is mandatory if you want to update Docker containers via Portainer that are served via the Github registry.)
14. Click on +Add registry then Custom registry. In the Name field area type in CODEBERG and in the Registry URL area type in codeberg.org. Click Add registry to save the settings. (Note: The codeberg.org registry is mandatory if you want to update Docker containers via Portainer that are served via the codeberg.org registry.)
15. Click on +Add registry then Custom registry. In the Name field area type in Quay.io and in the Registry URL area type in quay.io. Click Add registry to save the settings. (Note: The quay.io registry is mandatory if you want to update Docker containers via Portainer that are served via the quay.io registry.)
16. Done.