Docker installation guide Synology

[josdegroot]

Request

Is is possible to make a manual to install the DSMR docker on a synology. For me it's not clear now wich volumes i have to map for example.

Hopefully someone can help me with the installation. Like this for example: https://github.com/koush/scrypted/wiki/Installation:-Docker-Synology-NAS

Additional information

No response

[xirixiz]

Hi Jos, to be honest, not really :). It's more related to Docker and how to use Docker.

To get you started:

• Docker works with images. Docker images are static.

• Running a Docker image will create a Docker container.

• A Docker image is static, a Docker container isn't. So each time you start a Docker container you can modify stuff within that container. However, when you restart the container, it'll use the Docker image, so the Docker container starts "clean" again. So all settings and modifications will be lost.

• Now volumes come into play. You can map/mount folders and/or volumes into your Docker container from the Docker host (Synology in your case). So eacht time you start your container you mount the folder/volume in your container so settings will be stored to that location. So when restarting a container, the data from your Synology will be mounted again so you still have the same data available (persistent storage).

So in case of DSMR it requires two Docker containers. One for the application and one for the database. You most probably would like to keep settings and data from the database each time you restart the DSMR Docker database container, so therefor you mount the data folder from your Synology to that container. This can be either a simple folder or you can use Docker volumes (both heb pros and cons).

I hope this will help you. There is also a docker-compose example in the repo btw.

Besides that search for the terms I mentioned and follow some Docker tutorials on youtube, that way you'll learn the quickest and you should be able to have DSMR up and running in no time. Ofcourse, if you have any questions, don't hesitate to ask.

[josdegroot]

Hi Xirixiz,

Thanks for your quick reply. What matters more is that it is not clear to me which volume I should map with DSMR on the docker side (I can find the local folder on my synology). But which volume mounts does DSMR use internally.

In addition, it is not yet clear to me how I should create the correct Database within Postgres. I have Postgres running but if i start de DSMR docker I get this:

date	stream	content
2022-06-07T07:19:41.849151809Z	stdout	[s6-finish] sending all processes the KILL signal and exiting.
2022-06-07T07:19:38.838162688Z	stdout	[s6-finish] sending all processes the TERM signal.
2022-06-07T07:19:38.707497822Z	stdout	Testing database connectivity: 20 second(s) of 30 seconds...nc: getaddrinfo: Name does not resolve
2022-06-07T07:19:38.597756036Z	stdout	[s6-finish] waiting for services.
2022-06-07T07:19:38.597568125Z	stdout	[cont-finish.d] done.
2022-06-07T07:19:38.597236242Z	stdout	[cont-finish.d] executing container finish scripts...
2022-06-07T07:19:38.238393503Z	stdout	Testing database connectivity: 19 second(s) of 30 seconds...nc: getaddrinfo: Name does not resolve
2022-06-07T07:19:38.238373690Z	stdout	Testing database connectivity: 18 second(s) of 30 seconds...nc: getaddrinfo: Name does not resolve
2022-06-07T07:19:38.238351397Z	stdout	Testing database connectivity: 17 second(s) of 30 seconds...nc: getaddrinfo: Name does not resolve
2022-06-07T07:19:38.238302036Z	stdout	Testing database connectivity: 16 second(s) of 30 seconds...nc: getaddrinfo: Name does not resolve
2022-06-07T07:19:33.694268718Z	stdout	Testing database connectivity: 15 second(s) of 30 seconds...nc: getaddrinfo: Name does not resolve
2022-06-07T07:19:32.691511930Z	stdout	Testing database connectivity: 14 second(s) of 30 seconds...nc: getaddrinfo: Name does not resolve
2022-06-07T07:19:31.688777013Z	stdout	Testing database connectivity: 13 second(s) of 30 seconds...nc: getaddrinfo: Name does not resolve
2022-06-07T07:19:30.685628489Z	stdout	Testing database connectivity: 12 second(s) of 30 seconds...nc: getaddrinfo: Name does not resolve
2022-06-07T07:19:29.677851290Z	stdout	Testing database connectivity: 11 second(s) of 30 seconds...nc: getaddrinfo: Name does not resolve
2022-06-07T07:19:28.675356401Z	stdout	Testing database connectivity: 10 second(s) of 30 seconds...nc: getaddrinfo: Name does not resolve
2022-06-07T07:19:27.672852336Z	stdout	Testing database connectivity: 9 second(s) of 30 seconds...nc: getaddrinfo: Name does not resolve
2022-06-07T07:19:27.594583246Z	stdout	Testing database connectivity: 8 second(s) of 30 seconds...nc: getaddrinfo: Name does not resolve
2022-06-07T07:19:27.594564286Z	stdout	Testing database connectivity: 7 second(s) of 30 seconds...nc: getaddrinfo: Name does not resolve
2022-06-07T07:19:27.594543621Z	stdout	Testing database connectivity: 6 second(s) of 30 seconds...nc: getaddrinfo: Name does not resolve
2022-06-07T07:19:27.594515905Z	stdout	Testing database connectivity: 5 second(s) of 30 seconds...nc: getaddrinfo: Name does not resolve
2022-06-07T07:19:27.594459054Z	stdout	Testing database connectivity: 4 second(s) of 30 seconds...nc: getaddrinfo: Name does not resolve
2022-06-07T07:19:21.657756224Z	stdout	Testing database connectivity: 3 second(s) of 30 seconds...nc: getaddrinfo: Name does not resolve
2022-06-07T07:19:20.655007178Z	stdout	Testing database connectivity: 2 second(s) of 30 seconds...nc: getaddrinfo: Name does not resolve
2022-06-07T07:19:19.652156543Z	stdout	Testing database connectivity: 1 second(s) of 30 seconds...nc: getaddrinfo: Name does not resolve

[xirixiz]

Het lijkt erop dat de DSMR container de Postgres container niet kan resolven. Dit hangt weer af van op wat voor manier je de ccontainer start. Gebruik je een bridge netwerk, host netwerk...welke naamgeving gerbuik je voor de container, etc? Dat is belangrijk om te weten om ervoor te zorgen dat ze zichtbaar zijn voor elkaar. Je hoeft overigens geen db te maken, dat regelt DSMR voor jou wanneer de connectie tot stand is gekomen ;).