Updated: April 24, 2019
The short answer is Yes.
Shoko Server is the back-end of the entire Shoko suite, which means every single program and plugin provided uses it for accessing and maintaining your anime collection. This makes Shoko Server mandatory and also means Shoko Server must be running to use any of the programs or plugins that connect to it. With the exception of file importing, Shoko Server is no more resource intensive than other programs you probably have running in the background so you don’t need to worry about Shoko Server eating up resources.
Installing Docker will depend on what distribution you are running.
For most users installing docker from their package manager is advised, this way you will keep up with the latest updates and security updates. On the homepage of Docker you can find the installation procedure for your distribution of the Docker Community Edition.
The latest Docker image is available on Docker Hub. To get the image run the following in the command line.
docker pull cazzar/shokoserver
To run a basic docker container for Shoko Server, you can run the following from the command line.
docker run -p 8111 cazzar/shokoserver
This command will run a new empty docker instance with Shoko Server installed. At the same time port 8111 will be made available on the host to reach Shoko Server remotely. At this point you’ll be able to use Shoko Desktop to connect to the server.
Simply put, you are binding the port on container to the port on host, otherwise a random port will be chosen on the host.
TCP is used since UDP is not required.
To preserve settings between updates, the settings folder must be remapped to a location outside the container.
In order for Shoko Server to manage your collection, you must map at least one volume to the container.
Note: You can have multiple volumes, and they can be named any way you like (/anime, /tv_shows, /media, etc.)
Optional: You may also map a import volume, there is no difference between this and the previous command - This is just another example to illustrate how adding additional volumes work.
Note: You can have multiple volumes, and they can be named any way you like (also try: /downloads, /completed_torrents, etc.)
Putting everything together will get us the following configuration
docker run -d --name shokoserver --restart always -p 8111:8111/tcp -v "/path/to/shoko/settings:/home/shoko/.shoko" -v "/path/to/anime:/anime" -v "/path/to/import:/import" cazzar/shokoserver
This will provide you a Docker Shoko Server instance that runs in the background with persistent configuration, as well as expose it on your server to connect with Shoko Desktop / WebUI.
Note: If you run the Docker container as any other uid/gid other than the default Shoko user see the Advanced Settings section.
Open Docker from the Main Menu, select Docker Registry and than click the Settings button at the top.
By default, Synology’s Docker is only configured to allow images downloaded from it’s own private registry. Shoko Server is published to the Docker Hub, and that registry needs to be added to Synology Docker.
Click the Add button to add a new entry and input the following information.
|Registry Name||Docker Hub|
|Trust SSL Self-Signed Certificate||✔|
Once down, click Confirm and then Close.
You can now search repositories from the Docker Hub Registry. Enter cazzar/shokoserver into the search box above and click the Search button.
Check to make sure your results are accurate and click on the cazzar/shokoserver to chose a release to download.
After selecting the release, a notification under images will appear and Shoko Server download will begin.
Wait for the download to complete, then click Launch to create a container for Shoko Server (download size may differ).
Click on Advanced Settings.
While not required, we recommend checking Enable Auto Start to start the container automatically.
Learn more about Enable Auto Restart.
Once done, click on Volume.
Here you will mount volumes to folders on the host. This is done to preserve your settings between updates and to grant the container access to your shared folders.
Click on Port Settings to continue.
To make management easier, we can combine all the previous items in a docker compose file.
In order to make this work, install docker-compose, a guide how to can be found here on the Docker website. Once docker-compose is installed create a docker-compose.yml file anywhere on your system. Open the file and put the following inside.
version: "3" services: shoko_server: container_name: shokoserver image: cazzar/shokoserver restart: always ports: - "8111:8111/tcp" volumes: - "/path/to/config:/home/shoko/.shoko" - "/path/to/anime:/anime" - "/path/to/import:/import"
This combines all of our previous configuration in an easy to read and edit format, and will allow you to create a powerful startup script that could (for example) include a MySQL server, a download client, and anything else you can think off that’s available in a docker format.
While viewing the Docker panel in the Synology web interface, click on Container to view the running containers.
If everything was set up correctly, Shoko Server should be automatically running and the details button will become available. Select the container and then click Details.
Here you can view and verify the Port settings and volume settings, as well as other information.
Once done, click Terminal.
The terminal view gives you the output of the Shoko Server session. It is a useful aid in quickly determining if there is an issue.
Running shoko via docker has some additional features / options that might be useful some users.
In order to run the docker as a specific UID / GID you can specify it in the environment variables.
By default shoko runs with UserID 1000 and GroupID 100.
To make docker run as a certain user/group you can define this through the ENV variables.
This makes working with permissions a lot easier since you can match your docker with the local accounts on your machine withoutdoing much work
If you getting errors with Denied folder access then the wrong PUID and PGID could be the cause.
PGID 101 should be your admin group.
To find the PUID on any user, login with said user with SSH or Telnet with Putty or something similar with the
The default settings.json is stored within the image. When Shoko Server for Linux is started for the first time, it checks for the presence of settings.json and if it does not exist, then it copies the one from the image.
If at any time you need to reset the configuration back to the default settings, shut down Shoko Server for Linux and delete the settings.json file.
To create the settings.json file, start Shoko Server for Linux.
Volume can be mounted to relocate files.
Default Location for settings.json.
Please note that this is the location as seen within the container.
Depending on your installation, the actual location for settings.json may be in an alternate location.
Since Shoko Server for Linux runs without a graphical interface configurations must be made to the configuration file directly. Please note that the configurations shown below are the minimum required configurations needed to start the server. Not all configurable options are defined below. The default settings.json is stored within the image. When Shoko Server for Linux is started for the first time, it checks for the presence of settings.json. If it does not exist, it will copy the default one from the image. If at any time you need to reset the configuration back to the default settings, shut down Shoko Server for Linux and delete the settings.json file. To create the settings.json file, start Shoko Server for Linux.
Previously, Shoko did support both MySQL and SQL Server as possible database options due to an issue regarding some issues when using SQLite with a large collection. Starting with Version 3.6, we’ve been steadily making improvements to address this issue that the benefits once provided by MySQL and SQL Server are negligible. To that end support for MySQL and SQL Server as a database option has been deprecated.
Users who are currently using either MySQL or SQL Server can still edit their database information by directly editing settings.json located in the configuration folder defined in the docker run command.
|"DatabaseType": "SQLite",||"SQLite", "SQLServer", "MySQL"||By default it should be SQLite.|
|"SQLServer_DatabaseServer": "localhost",||"localhost", "xxx.xxx.xxx.xxx"||SQLServer ONLY: This is the IP Address of the SQL Server|
|"SQLServer_DatabaseName": "",||"Shoko Server", "my_existing_name"||SQLServer ONLY: This is the name of the SQL Server Database. If the database does not exist then it will be created.|
|"SQLServer_Username": "",||"sa","my_existing_username"||SQLServer ONLY: This is username for the SQL Server Database.|
|"SQLServer_Password": "",||"my_sql_password"||SQLServer ONLY: This is the password for the user account above, to be used for the SQL Server Database.|
|"MySQL_Hostname": "localhost",||"localhost", "xxx.xxx.xxx.xxx"||MySQL ONLY: This is the IP Address of the MySQL Server|
|"MySQL_SchemaName": "",||"Shoko Server", "my_existing_name"||MySQL ONLY: This is the name of the MySQL Server Schema. If the schema does not exist then it will be created.|
|"MySQL_Username": "",||"root","my_existing_username"||MySQL ONLY: This is the username for the MySQL Server Database.|
|"MySQL_Password": "",||"my_mysql_password"||MySQL ONLY: This is the password for the user account above, to be used for the MySQL Server Database.|
|"AniDB_Username": "",||"","my_AniDB_Username"||OPTIONAL: This is your AniDB username. It is recommended to add your username if you are using an existing database.|
|"AniDB_Password": "",||"","my_AniDB_Password"||OPTIONAL: This is your AniDB password. It is recommended to add your username if you are using an existing database.|