synology-docker

📄 Originally forked from markdumay/synology-docker

An Unofficial Script to Update or Restore Docker Engine and Docker Compose on Synology NAS

About • Built With • Prerequisites • Deployment • Usage • Contributing • Credits • Donate • License

About

⚠️ The repository 'Synology-Docker' is not supported by Synology and can potentially lead to malfunctioning of your NAS. Use this script at your own risk. Please keep a backup of your files.

⚠️ If you're using the Nvidia driver on your synology, you will need to re-start the Nvidia driver, or re-run nvidia-ctk runtime configure to re-add the nvidia runtime after each run of this script in order for the driver to get re-added to docker.

❗ Portainer Users - Portainer currently has an issue where it persists the first-used logging driver alongside container definitions. You may have to completely recreate (or duplicate and edit) containers created in portainer to use the local log driver. It would be best to do that with all of your containers BEFORE running this update. Portainer has created some challenges for users migrating from one log driver to another. It also has created problems with networks and port definitions not translating... You will have to spend way more time re-creating and troubleshooting containers after this update than if you're trying to use portainer. So... if you're using portainer and you use this update... you have been warned... things will not be smooth. docker-compose is the way to go.

Synology is a popular manufacturer of Network Attached Storage (NAS) devices. It provides a web-based user interface called Disk Station Manager (DSM). Synology also supports Docker on selected models. Docker is a lightweight virtualization application that gives you the ability to run containers directly on your NAS. The add-on package provided by Synology to install Docker is typically a version behind on the latest available version from Docker. Synology-Docker is a POSIX-compliant shell script to update both the Docker Engine and Docker Compose on your NAS to the latest version or a specified version.

Built With

The project uses Docker, a lightweight virtualization application.

Prerequisites

Synology-Docker runs on a Synology NAS with DSM 6 or DSM 7. The script has been tested with a DS918+ running DSM 6.2.4-25556, DSM 7.0.1-42218, and DSM 7.2.1-69057. Other prerequisites are:

• SSH admin access is required - Synology-Docker runs as a shell script on the terminal. You can enable SSH access in DSM under Control Panel ➡ Terminal & SNMP ➡ Terminal.

• Docker is required - Synology-Docker updates the binaries of an existing Docker installation only. Install Docker on your NAS in DSM via Package Center ➡ All Packages ➡ ContainerManager and ensure the status is Running.

• SynoCommunity/Git is required - Synology-Docker needs the Git package from SynoCommunity installed on your NAS. Install Git on your NAS by adding the SynoCommunity package repository (described here) and installing the Git package in DSM via Package Center ➡ Community ➡ Git.

Deployment

Deployment of Synology-Docker is a matter of cloning the GitHub repository. Login to your NAS terminal via SSH first. Assuming you are in the working folder of your choice, clone the repository files. Git automatically creates a new folder synology-docker and copies the files to this directory. Then change your current folder to simplify the execution of the shell script.

git clone git@github.com:telnetdoogie/synology-docker.git
cd synology-docker

Preparation before upgrade

If you're using compose for your containers, I highly recommend that before you run the upgrade (or restore, if you're going back to the original version) you go through and stop each running container.

cd /volume1/docker/{my_container}
docker-compose down

Because this upgrade modifies the default logger for docker, stopping (removing) and re-starting each container is required, since the logging mechanism is persisted during a compose docker build / start. You don't HAVE to do this before the upgrade, however if you don't, you'll get errors related to the logger for your containers, and will have to stop and start each container / stack after the upgrade anyway.

Stopping all the containers prior to the upgrade / restore will also make the upgrade a lot faster, since the service stop and restart normally has to do the work of stopping and starting all containers.

For a convenient way of enumerating all of the running compose projects, run the script:

./syno_docker_list_containers.sh

...if you see a container listed with !---not_managed_by_compose---! you'll need to make sure you know how to:

1. Remove this container
2. Recreate this container after the upgrade (which will default to the new logging driver) The syno_docker_list_containers.sh script will attempt to make a suggestion about how to re-create the container, however if you have the original script or command, you should use what you know. The script may not be 100% correct.

Usage

Synology-Docker requires sudo rights. Use the following command to invoke Synology-Docker from the command line.

sudo ./syno_docker_update.sh [OPTIONS] COMMAND

Commands

Synology-Docker supports the following commands.

Command	Argument	Description
backup		Create a backup of Docker binaries (including Docker Compose), dockerd configuration, and Synology's start-stop-status script
download	PATH	Download Docker and Docker Compose binaries to PATH
install	PATH	Update Docker and Docker Compose from files on PATH
restore		Restore Docker and Docker Compose from a backup
update		Update Docker and Docker Compose to a target version (creates a backup first)
logger		Update ONLY the logging-driver. This is a good first step to remove the dependency on the synology logger

Under the hood, the five different commands invoke a specific workflow or sequence of steps. The below table shows the workflows and the order of steps for each of the commands.

#	Workflow step	backup	download	install	restore	update	logger
A)	Download Docker binary		Step 1			Step 1
B)	Download Compose binary		Step 2			Step 2
C)	Extract files from backup				Step 1
D)	Stop Docker daemon	Step 1		Step 1	Step 2	Step 3	Step 1
E)	Backup current files	Step 2		Step 2		Step 4	Step 2
F)	Extract downloaded binaries			Step 3		Step 5
G)	Restore Docker binaries				Step 3
H)	Install Docker binaries			Step 4		Step 6
I)	Update log driver			Step 5		Step 7	Step 3
J)	Restore log driver				Step 4
K)	Update Docker script			Step 5		Step 8
L)	Restore Docker script				Step 5
M)	Start Docker daemon	Step 3		Step 6	Step 6	Step 9	Step 4
N)	Clean temp folder					Step 10

• A) Download Docker binary - Downloads an archive containing Docker Engine binaries from https://download.docker.com/linux/static/stable/x86_64/docker-${VERSION}.tgz. The binaries are compatible with the Intel x86 (64 bit) architecture. Unless a specific version is specified by the --docker flag, Synology-Docker pulls the latest stable version available.
• B) Download Compose binary - Downloads the Docker Compose binary from https://github.com/docker/compose/releases/download/${VERSION}/docker-compose-Linux-x86_64. Unless a specific version is specified by the --compose flag, Synology-Docker pulls the latest stable version available.
• C) Extract files from backup - Extracts the files from a backup archive specified by the --backup flag to the temp directory (/tmp/docker_update).
• D) Stop Docker daemon - Stops the Docker daemon by invoking synoservicectl --stop pkgctl-Docker.
• E) Backup current files - Creates a backup of the current Docker binaries, including Docker Compose. The configuration of the logging driver and Synology's start-stop-status script are included in the archive too. The files included refer to /var/packages/Docker/target/usr/bin/*, /var/packages/Docker/etc/dockerd.json, and /var/packages/Docker/scripts/start-stop-status.
• F) Extract downloaded binaries - Extracts the files from a downloaded archive to the temp directory (/tmp/docker_update).
• G) Restore Docker binaries - Restores the Docker binaries in /var/packages/Docker/target/usr/bin/* with the binaries extracted from a backup archive.
• H) Install Docker binaries - Installs downloaded and extracted Docker binaries (including Docker Compose) to the folder /var/packages/Docker/target/usr/bin/.
• I) Update log driver - Replaces Synology's log driver with a default log driver local to improve compatibility while optimizing writes and limiting log file growth. The configuration is updated at /var/packages/Docker/etc/dockerd.json
• J) Restore log driver - Restores the log driver (/var/packages/Docker/etc/dockerd.json) from the configuration within a backup archive.
• K) Update Docker script - Updates Synology's start-stop-status script for Docker to enable IP forwarding. This ensures containers can be properly reached in bridge networking mode. The script is updated at the location /var/packages/Docker/scripts/start-stop-status.
• L) Restore Docker script - Restores the start-stop-status script (/var/packages/Docker/scripts/start-stop-status) from the file within a backup archive.
• M) Start Docker daemon - Starts the Docker daemon by invoking synoservicectl --start pkgctl-Docker (or synopkg start ContainerManager on DSM 7).
• N) Clean temp folder - Removes files from the temp directory (/tmp/docker_update). The temporary files are created when extracting a downloaded archive or extracting a backup.

Options

Synology-Docker supports the following options.

Option	Alias	Argument	Description
-b	--backup	NAME	Name of the backup (defaults to docker_backup_YYMMDDHHMMSS.tgz)
-c	--compose	VERSION	Specify the Docker Compose target version (defaults to latest available on github.com)
-d	--docker	VERSION	Specify the Docker target version (defaults to latest available on docker.com)
-f	--force		Force the update and bypass compatibility check / confirmation check
-p	--path		Path of the backup (defaults to current directory)
-s	--stage		Stage only, do not replace binaries or the configuration of log driver

Contributing

1. Fork the repository and create a new branch
2. Make and test the changes
3. Submit a Pull Request with a comprehensive description of the changes back to this repository

Credits

Synology-Docker is inspired by this gist from Mikado8231.

License

Origin

Forked from markdumay/synology-docker