The general rule would be to use some non-system/default port like 1024 or above. So change auto value to a port of your choosing. Another reason why this is not needed is that you can use almost any port for the Local port value that you want. It can be reconfigured but you will have to do it on the image level, so not important for now. DO NOT change the container side numbers, or you will have problems running the container in the 1st place. Left side localhost ports (on your NAS), right side container ports. Same as with volumes, ports are configured the same way. Meaning you will access those apps and services using your local NAS IP address and a custom port defined on the following tab, Port Settings. This will mean that all containers using this network will be essentially in a NAT configuration with your NAS. In the spirit of this tutorial just use the bridge. You can make new networks for specific subnets or you can use the default one, bridge. Here you can select networks that you want your container to use. You can (and preferred to do so) backup those folders as they are essential unlike the rest of the container that's expendable. This, as a result, will mean that all my data will actually be in docker/bitwarden folder on my nas and not sandboxed in the container itself. Ofc you don't have to use that destination if you don't want to) to /data folder that BW image is using. So to recap, I have mapped docker/bitwarden local path (bitwarden is a subfolder of /docker folder that you will get after you install Docker. In the case of this BitWarden image, all data is stored in /data folder as indicated by instructions on the image web page. The left side is your local NAS destination where you want container folder data stored. In the image above I have mapped the left side (your NAS folder structure) to the right side (container mount path). Moving your data around regardless of what's hosting your container. As a result, even if something happens to the container your data will be safe and all you have to do is recreate the container and attach it to the same volume to get access to your data. The Volume tab is used to map files or folders from within the container outside to your local shared folder(s) on your NAS. That means that in the case of BW, all your imported data, long random passwords that you have defined are gone! Now that you have understood the importance of this let's configure an outside volume that will keep your data safe from this scenario. As a result, all your work will be reset and gone. This means that after you restart your container (reboot, NAS update, Docker update, docker image update) it will reset itself to initial settings. If you start working with your container, all information, configuration, data etc, are sandboxed inside the container. Read up on those so that I don't start messing with this tutorial too much, but in short, it means this. Now, this is the most important thing that needs to be done when working with containers. I use Heimdall for all my docker URL needs so this option is OFF (again, you can use it if you choose to do so). The desktop in this context is DSM desktop, not your computer desktop. Regarding shortcuts on the desktop, personally, I don't use it. Ofc this is an optional setting but still. The Auto-restart feature is nice to have ON in case you need to reboot your nas or Docker for that matter and want all your containers booting automatically. Support for it can be reached on their Matrix chat channel if needed.Īfter you have installed Docker open it up and you will land on a similar screen Its updated and maintained all the time so there is no need to worry. This tutorial will focus on a custom vaultwarden/server image that I use as well. If your NAS is from the '+' lineup, then you are good to go. Keep in mind that this is not 100% supported and some features of docker will still not function. After that, you can use the Manual install button in Package Center to install Docker. "SIGNUPS_ALLOWED=false" #true or false if you want to enable or disable public signupsĬonsidering that there are several people interested in this solution, maybe a quick tutorial on how to run this in docker will help.ġst thing - install Docker via Package center or if your NAS doesn't support it, install it manually by downloading the package from Syno site. "SMTP_PASSWORD=password" #add SMTP_XXXX variables to allow public user managment (account reset etc)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |