The unofficial Synology forum for NAS owners and enthusiasts. Whether you need support for your Synology NAS device or other network matters, our well-educated users are at your disposal. Docker BitWarden - self hosted password manager using bitwardenrs/server image: Docker Firefly III - self-hosted manager for your personal finances: Docker Install nginx-proxy-manager: App Synology DS Manager – Download Station macOS app and Safari Extension 2020 NEW. Drabisan, For sure I already raised a ticket to Synology. But it will take time. In the meantime, I can satisfy my family with the plex solution I also found that it is possible to implement a SMB1 server working for the SONOS inside a Docker. Inside the Docker Image, openHAB is installed to /openhab. The install is a manual installation so all of the files are located here. This is also set as the home directory of the openhab user. The Image has a very minimal installation of Linux with no services running and just enough installed to allow openHAB to run. # Installation through Docker. Qnap d4 pro install problem. Synology DNS docker problem. Synology-nas, docker. 6: 88: March 23, 2021 Temp Folder old Partial.
I have recently purchased a Synology DS718+ and found out that amongst the many great things we can do with it, one is installing a WordPress site using the Web Station package. But it only lets us install one instance of WordPress. It is possible to manually install and run multiple WordPress sites on Synology NAS. But first of all, you have to read my introduction article “How to speed up WordPress on Synology NAS“.
If you use multiple computers in your house running any OS (Windows 10, Mac or Linux Ubuntu) and would like to pick up WordPress development on your localhost that you have left off on another computer in your home network without dealing with Dropbox, Onedrive, sync for files and a plugin like WP Migrate DB Pro for the database, read on.
After following these steps you should be able to create multiple websites on your localhost like this: local.dev, showcase-pro.dev which are accessible from any device on your network (that you can add a hosts entry in).
In this article I am not going to cover what’s required to make these sites accessible from outside your local WiFi/home network. You can find this information on host from home article. So, let’s start:
Please Support My work by Making a Donation.
- Log into your NAS LAN. In my case, it is at http://10.0.0.60:5000/.
- Go to Package Center, search for Web Station and install it. This will create a “web” folder in your NAS’s root.
- Also, install WordPress package and set it up. While we are not going to use the website created by this package (you may, if you wish), we take this step so that the needed dependencies like PHP, MariaDB 10 can get installed.
- Install the latest phpMyAdmin and Apache HTTP Server 2.4 packages. These are the relevant packages that I have running: Apache HTTP Server 2.2, Apache HTTP Server 2.4, MariaDB 10, PHP 5.6, PHP 7.0, PHP 7.2 phpMyAdmin, Web Station and WordPress. Some of these may not be needed. You might want to experiment with them.
- From the Main Menu, launch File Station. Navigate to web folder and create a folder for your site, say, “wordpress-latest”. Go inside the folder. Download WordPress on your computer, extract the zip, drag all the content and drop inside “wordpress-latest”. Alternatively, if you have Download Station package installed you can simply enter https://wordpress.org/latest.zip for the URL and have the file downloaded to “wordpress-latest”, then extract using the option from context menu.
- Create a folder for your website. Ex. showcase-pro.
- Copy all the content from “wordpress-latest” into the site’s folder.
- Right click on the folder and click Properties. Go to Permissions tab. Create a new permission for “http” user granting all Write permissions.
- Log into your phpMyAdmin (at http://10.0.0.60/phpMyAdmin/ for me) using “root” as the username (password is blank/empty) or use the one you have set up when you installed MariaDB10. After logging in, change the password if you wish. Create a new database for your site. Ex.: showcasepro. During my experiments, the database connection wasn’t working because the database name had a hyphen in it, so I had to change the database name from “showcase-pro” to “showcasepro”.
- In Windows Explorer/Finder, navigate to your Synology’s network drive and then into your website’s folder.
Rename wp-config-sample.php
to wp-config.php
and edit it. Set your database name, enter root
as username and your password.
Above
paste
If you are using MariaDB 10, edit wp-config.php parameter for hostname as follows:
Set new unique keys and salts generated at https://api.wordpress.org/secret-key/1.1/salt/
Save and close the file.
- Launch Web Station. General Settings: Set HTTP back-end server to Apache HTTP Server 2.4 and PHP to 7.2.
- PHP Settings: Set PHP version to 7.2. Leave PHP Cache enabled. Select these extensions: curl, exif, ftp, gd, gettext, iconv, mcrypt, mysqli, openssl, posix, soap, sockets, xmlrpc, zip. Press Apply.
- Virtual Host: Click Create, enter “showcase-pro.dev” for the Hostname, browse your site’s folder for Document root, select Apache HTTP Server 2.4 and PHP 7.2. Press OK.
- In your hosts file enter 10.0.0.60 showcase-pro.dev Do this for every computer from which you’d like to work on your local site.
- Visit http://showcase-pro.dev in your browser and complete the WordPress installation.
- Log into your WordPress site’s admin, go to Settings > Permalinks and press Save to generate the .htaccess or otherwise pretty permalinks will not work.
That’s it. Now you should be able to administer and access your newly created local WordPress site on any computer in your LAN network.
Note: If you have a https problems when accessing your .dev website try to change or reinstall using .local domain instead of .dev domain
This post was updated on Monday / October 5th, 2020 at 7:09 AM
1. Installation
Simply find and install a Docker application from the Synology Package Center.
Note: If you do not find the application in your Package Center, your Synology is most probably not supported yet:
Due to the hardware requirement, Docker will be only available on the following models:
18 series: DS3018xs, DS918+, DS718+, DS218+
17 series: FS3017, FS2017, RS18017xs+, RS4017xs+, RS3617xs+, RS3617xs, RS3617RPxs, DS3617xs, DS1817+, DS1517+
16 series: RS18016xs+, RS2416+, RS2416RP+, DS916+, DS716+II, DS716+, DS216+II, DS216+
15-series: RC18015xs+, DS3615xs, DS2415+, DS1815+, DS1515+, RS815RP+, RS815+, DS415+
14-series: RS3614xs+, RS3614xs, RS3614RPxs, RS2414RP+, RS2414+, RS814RP+, RS814+
13-series: DS2413+, RS3413xs+, RS10613xs+, DS1813+, DS1513+, DS713+
12-series: DS3612xs, RS3412xs, RS3412RPxs, RS2212RP+, RS2212+, DS1812+, DS1512+, RS812RP+, RS812+, DS412+, DS712+
11-series: DS3611xs, DS2411+, RS3411xs, RS3411RPxs, RS2211RP+, RS2211+, DS1511+, DS411+II, DS411+
10-series: DS1010+, RS810RP+, RS810+, DS710+(source, last updated 09-29-2017)
2. How to use it?
When you start a Docker application, you will see an application menu on the left side:
- Overview
- Registry
- Image
- Container
- Log
Overview
Here you will see your running containers, i.e. your running applications including allocated memory and CPU resources.
The real command in Docker:
Registry
On the registry page, you can search for new images (the same as on the official site). You can also add some new repositories (in addition to the official site) in Settings.
The real command in Docker:
After you found your image (e.g. ubuntu in our case), you should download it to your Synology. All Images are read-only and you can use them multiple times for more containers.
Install Portainer Docker Synology
The real command in Docker:
Image
Here you will find images available on your Synology, ready to create new containers using a wizard or directly with a docker run
command. You can usually find this command on the official page with an image.
The real command in Docker:
We use a long running process for creating a new container from a docker run
command:
The Synology wizard checks your command for compatibility, not all docker run
parameters are available for use.
- Docker run supports the below parameters:
'd', 'detach'
'e', 'env'
'link'
'm', 'memory'
'name'
'P', 'publish-all'
'p', 'publish'
'privileged'
'v', 'volume'
- Docker run does not support the below parameters:
'a', 'attach'
'add-host'
'c', 'cpu-shares'
'cap-add'
'cap-drop'
'cidfile'
'cpuset'
'device'
'dns'
'dns-search'
'entrypoint'
'env-file'
'expose'
'h', 'hostname'
'i', 'interactive'
'lxc-conf'
'net'
'restart'
'rm'
'security-opt'
'sig-proxy'
't', 'tty'
'u', 'user'
'w', 'workdir'
Basically, your containers need to run as a daemon on your Synology (an opposite to run an interactive shell). It makes sense, you cannot run an interactive shell in your Synology Docker application in a web browser.
Back to our new ubuntu container (actually got name dummyUbuntu). The wizard offers to set more options, but we want to create a dummy container, so click Next, Next, Next.
Container
The dummyUbuntu container appears now on the Container page.
The real command in Docker (prints all containers including stopped):
The last step is waiting for us: Run it.
When you double click on any container, a window with some more details about a running container appears.
You see some information about our dummyUbuntu container and capability to Start, Stop, Restart it.
Install Jackett Synology Docker
The real command in Docker:
You can see other information about a running container using the top menu.
The real command in Docker:
On the Log tab, you can see logs from your container (not automatically refreshed, maybe in the future with the parameter -f
as available in the standard Docker client).
The real command in Docker:
The last tab Terminal shows output of a command used to run your container (in our case the dummy long running process: 'while true; do echo hello world; sleep 1; done'
)
The real command in Docker:
Note: The docker attach
command never starts a new instance of a shell, instead of that you will see an ongoing output of the first start command. For more alternatives, see the point 8 on page 10 Useful Docker Commands – Tips and Tricks.