How to run Portainer on a Synology container manager
What is Portainer :
Portainer is a container management platform that simplifies the deployment and management of containerized applications. It provides a user-friendly web interface for managing Docker, Kubernetes, and Podman environments, allowing users to visualize containers, images, volumes, and networks without needing to use complex command-line tools. Portainer is widely used, with over 650,000 users, and is designed to make container management accessible to everyone, regardless of their technical expertise
Step 1
Install Container manager if not installed already. Find a guide Here.
Step 2
Create a Portainer folder for all the data.
Step 3
Go to the Container Manager and open the Project tab. Click on the Create button to create a new project. Define the path of the portainer folder previously created (don’t just blindly follow my screenshots). You’ll paste the Docker Compose yaml configuration here in the next step
Step 4
Update the below docker compose.yaml to accomodate our needs. For me, I had conflicts with some of my ports, so I re-mapped them. Also make sure you define the volume path for your portainer data.
version: '3'
services:
system.portainer:
image: portainer/portainer-ce:latest
container_name: system.portainer
hostname: portainer
restart: unless-stopped
mem_limit: 128m
mem_reservation: 48m
cpu_shares: 128
ports:
- "1000:8000" #CHANGE_IF_CONFLICT
- "2000:9000" #CHANGE_IF_CONFLICT
- "9443:9443" #CHANGE_IF_CONFLICT
security_opt:
- no-new-privileges:true
environment:
- PUID=1234 #CHANGE_TO_YOUR_UID
- PGID=6754 #CHANGE_TO_YOUR_GID
volumes:
- /etc/localtime:/etc/localtime:ro
- /var/run/docker.sock:/var/run/docker.sock
- /volume2/docker1/portainer:/data #CHANGE_TO_YOUR_PATH
logging:
driver: json-file
options:
max-file: "3"
max-size: "10m"Not sure on what your PUID and PGID are go here to find out more.
Open your browser and type in http://Synology-ip-address:9000 Follow the instructions in the image below. Choose a Username and a strong Password, confirm the password, then press Create user.
STEP 7
Click Get Started (proceed using the local environment in which Portainer is running). Follow the instructions in the image below.
STEP 8
On the right in the Environments are, click on the little pencil. Follow the instructions in the image below.
STEP 9
After you click on the little pencil a new page will open. On the Public IP area type in your own NAS Local IP which, in this example’s case, is 192.168.1.18 then click Update environment. Follow the instructions in the image below. If everything goes right, you will see this message at the top right of your screen: “Environment updated“.
STEP 10
On the left Portainer sidebar, click on Registries then Click + Add registry. Follow the instructions in the image below.
STEP 12
Click on Custom registry. In the Name field area type in GHCR and in the Registry URL area type in ghcr.io
Click Add registry to save the settings. Follow the instructions in the image below.
Note: The ghcr.io registry is mandatory if you want to update Docker containers via Portainer that are served via ghcr.io registry.
STEP 13
Click on 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. Follow the instructions in the image below.
Note: The codeberg.org registry is mandatory if you want to update Docker containers via Portainer that are served via codeberg.org registry.
STEP 14
Click on 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. Follow the instructions in the image below.
Note: The quay.io registry is mandatory if you want to update Docker containers via Portainer that are served via quay.io registry.
STEP 15
Verify that everything went well and the registries are properly showing up. You should see something like this under Registries:
