Superb video... well researched, concise and easy to listen to. Packed with useful info. It consolidated a lot of vague knowledge I had around Docker, Synology's Docker UI and docker-compose. I suspect it won't be the last time I watch this. Small suggestion... you may want to lower your screen resolution (or up the scaling factorto 125%) while recording. Some screens had tiny text.
Thank you soo much. This covers all the basics I've needed to know for years. Every tutorial I've used for installing stuff on my Synology does nothing to describe what Docker is and how it works. And every Docker tutorial is way too in-depth with the software development side of things.
I wish I had watched this before trying to experiment my way through a working macvlan network so that I can reverse proxies on port 443 and then have the proxy be able to communicate to other containers as well as process on the host. I did manage to figure it out eventually myself but your video spells it out so clearly and concisely. Thanks a lot.
It is as basic as I can explain it, but from looking up the container you're trying to implement, it doesn't appear to be the most straight-forward. You might have to consult the documentation and really try and break it down and then go from there.
Oh thank god, I finally understand, thank you. The only piece of the puzzle missing now is how to run something in docker if it's not in a repository. Like say I have a .jar I want to run, would I have to create my own image with it? How do you make an image?
You can add an image from a file (in the Docker GUI). As far as making that image - I'm not sure unfortunately. I haven't created any of my own Docker containers :-(
Dont know if anyone cares but if you're stoned like me during the covid times then you can watch all of the latest movies on Instaflixxer. I've been watching with my girlfriend for the last weeks :)
This video is awesome. I do have a question what if there is no file or page that shows what volumes there are and how do you go about configuring it. I have a come across several docker images that didn't have this information.
Thanks! Some containers don't have volume mounts, but the ones with user data normally do. I don't think there's a way to find it after the download - you might just have to see if you can find it online unfortunately.
Thanks, I got some containers setup with the macvlan method. I can access them all locally but when connected to my network with either OpenVPN or Wireguard, I can't connect to the containers made with this method. Any help would be great!
How are you trying to access them, by IP address? Also, if you are - can you try and access them using the bridge IP address created alongside the macvlan network interface?
Thank you! I planned on creating a separate tutorial for this, but I will give you a brief overview now. Generally, the easiest way that I find to do it is to download the latest image, stop the container and then right-click it and duplicate settings. It will then create a new container with the same settings (and new image) where you can start it up and test to make sure everything is still working as expected. If it is, feel free to delete the old container. People have suggested that you can do it by "clearing" the existing container, but that does NOT work for me. I lose all my settings that way. I specifically left this out of the tutorial as I wanted to test this out further, so I will have a tutorial for it at some point!
as stated this is prolly the best explanation.. tho what i dont get if this made for synology why is it made so have to do stuff like mounting configuration etc... synology's credo is/was to keep it simple as possible we should only have to see yes and no buttons and the rest should be done by scripts and auto installs. (edit) Gave up allready could understand what i did and could not acces the web gui to get to qbittorrent.
I don't use qbittorrent so I can't comment, but the volumes are only necessary to preserve your files (so you can transfer them to a different device if necessary). You can create most containers without any volume mapping.
i'm stuck on creating the folder - when i add docker/twonky/config as file/folder, when i try to enter /config as the mount path i get the error "some of your settings are invalid, please enter them again" i can access the folder (docker/twonky/config) from filestation no problem. Any help would be appreciated!
I’m going to have to watch this several time to understand how to use docker I’ve just got my first synology nas ds920+ and I’m a complete noob I want Sonarr radarr and SABnzbd in docker and to replace Plex and put that in docker 😩😩 I have so much to learn about synology nas’s and how they run
It's a lot to learn, but if you take it slow, you will hopefully understand everything. Not necessarily only from my videos, but there are tons of great videos on these topics. Once it "clicks", it's pretty easy to understand!
The hard drives are linked to a storage pool and volume, so while you aren't linking them directly to the HDD, you're linking them to a file path which is part of a volume, which is part of a storage pool, which consists of HDDs. Hope that makes sense.
Thank you and quick question. If you create a container with docker compose will it appear in the GUI or is it invisible to DSM? If it is invisible is there a way to add it post deployment? Having the utilization visible of the containers is nice in order to see how your environment is performing and diagnosis of any future performance issues.
It will appear (you might have to logout and log back in), but you can only start/stop the container from the GUI, I believe. You should also be able to see the utilization. If you need to make any actual changes to it, you will have to edit the docker compose file and then recreate the container.
@@WunderTechTutorials I'll leave a sub then. The weird backup situation is what currently holds me back from setting it up. Why isn't there a simple "Backup" button on the UI which also let's you restore is beyond me. I know you can export the json, but apparently not Import it....
@@aliasname5518 Generally, Docker containers are meant to be portable, so you don't back up the container, you only back up the important data inside of that container.
Hi Frank, i don't have a NAS yet, so this might be an obvious question to some. Actually, i'm undergoing the process of understanding Docker, what it is and does, pros and cons and so forth. I understand it now from a developers (which i am not) perspective, but i often read about people running (not developing) applications in Docker, for example on their NAS. Can you help me understand why? Is it because you're not able to install any program you like on a NAS (Is there something like an 'app store')? If not, why not just install the applications on the NAS instead of running them in Docker? What are the pros and cons? I tried finding your emal so i could write you, but with no luck. Hope to hear from you! :)
runs on a smaller footprint, a dockercontainer is really small and only contains what it needs so it doesnt waste resources (which can be precious in a smaller nas with a weaker cpu+ram combo) why i use docker: i can run more services with docker on my weak small mini-pc.
There was a great response to this already, but I will add my two cents: Not all applications that you can run on Docker are supported packages on your NAS. That alone is one of the main reasons that people run Docker containers. Outside of that, you also have portability, so if you ever purchase a home server or simply want to run your Docker containers on a separate device, you copy the data, migrate the containers and everything will function as it did on your NAS. Finally, there are performance benefits (not that I think you'll run into any issues running the packages) as these are lightweight containers that don't take up many resources. Docker is AWESOME, and it's something you should definitely check out, but outside of a few specific scenarios, you'd basically be installing the same exact application as the package (assuming there is one), which makes this mostly a personal preference.
@@WunderTechTutorials Perfect thanks, installing docker and installing the image in docker isn't a problem. Once I run it, I'm assuming it should show up on my router with an IP Address but it never does.
@@Victork32 That is correct - if it's not getting an IP address, something is off. Could be a port conflict or it could be a more involved setup (which some containers need).
Hey Wunder, we're trying to install Mattermost via Docker on Synology. We followed your tutorial (really appreciate it) and got it all set up, but once we start the container it keeps getting our the same error every few seconds: Error: failed to load configuration: could not create config file: open /mattermost/config/config.json: permission denied. Why is this happening? We tried giving High privilege, but the result is the same. Any tips how to fix this? Thank you.
It could be a permission issue even though the container has high privilege. Have you created the config.json file? Played around with any permissions?
@@WunderTechTutorials thanks for the reply. No, I haven't created the config.json file. Do I have to create one? No official Mattermost guide says this, and since I'm fairly new to Docker use I might be wrong and it might be a basic thing that is not even mentioned in the guides. I even tried to fix it by creating a new user with read/write permission to docker, found his uid and gid through putty and set it under the Environment variables of the container. I tried disabling the firewall, thinking that it's maybe the culprit in this case (though that might not have anything to do with it), but the error persisted. What could be the cause?
@@RedMartyrEntertainment I can't say for sure as I haven't ever created a Mattermost container, but a lot of times, config.json files include some sort of database configuration. If it does, you're most likely better off trying to use Docker Compose through the terminal than Synology's GUI. Might just be easier that way.
the workaround with macvlan did not work - ports still being blocked (as error when try to start the container by console) - weirdly enough, the docker container got the same ip as the host, but i can ping outside the container, which is half of a success
When I try to download a new image I kept getting timeout. I tried changing my DNS to use cloudflare but still have the same timeout issue and cant download any new images. Do you have any idea on why this occurs and how I can fix it?
@@jimmycoconut88 I haven't seen it happen in a scenario where it wasn't DNS related. I would try and isolate what else isn't working (as other things most likely aren't working either, you just haven't come across them yet).
Great video, nice job! I'm experiencing issues with docker on the Synology NAS, I'm trying to run a container for my Tesla. Runs fine on RPI but issues on the NAS. Still investigating the issue. Anyon running Teslamate on the NAS?
G'Day and thanks so much for this great Tutorial. I just bought a Synology NAS and am brand new to Docker. This was invaluable. I'm now about to watch your tut on Docker Compose. Cheers.
This is great. I have an issue I'm trying to solve and would love to see if you have an easy solution. Using HAProxy I want to run a reverse proxy on the Synology NAS. Seems simple. I found a command to unbind 80 and 443 from the Synology server but I get a "cannot bind socket (permission denied)" error when I run up the HAProxy Docker container. What I think I need to do is run the "--sysctl net.ipv4.ip_unprivileged_port_start=0" flag but I don't know how to add this on a Synology server or if I can.
Hmm, if you're using HAProxy, any reason why you want to unbind 80/443 from the NAS? You should be able to set up the source as 443 and the destination (on your local network) as the DSM port.
@@WunderTechTutorials I'm confused by your reply. HAProxy is being used for reverse proxy. 443 is the standard port for https. in HAProxy (docker container) we have mapped it to 4443 but in docker in the translation table when we try to make that port 443 so there is no need to type a port into a browser (a UX pain) it won't let us. We just want to get a workaround for that part of the process. everything else seems to be working now. basic set-up; one customer-facing access to two microservices. all over HTTPS.
@@chrisschneider7609 My question is more on the Synology side as to why you're trying to unbind ports 80/443 on the NAS? I am assuming that you have HAProxy running on a difference device, so you should be able to leave the DSM port as 5001 (or something different, just not 80/443), and use port 443 on the HAProxy side without adjusting DSM at all.
@@chrisschneider7609 I would look into using a macvlan network interface for it then. I'm not a fan of unbinding 80/443, but ultimately, it's up to you.
I finally had it working but then i get error only to find out i used wrong adapter and now i cant add a new one, how do i remove it ? or am i fucked and forced to wipe my entire 14 tb nas just to fix one mistake ?
I have installed Nginx reverse proxy manager as a docker container on my Synology but if i request a certificate from Let's encrypt i get an internal error. I suspect that it has something to do with the port configuration. Since i work on a NAS where my Docker is installed I can't use port 80 and 443 for Nginx directly. i had to forward them with different port numbers on the Host. I think i can solve it if i connect the container to a different network. You think that's a good idea and what should i do?
I have a tutorial up for Nginx Proxy Manager in specific. Some people have issues with it, but you're correct in stating that it's probably port 80/443. Have you port forwarded the ports you mapped to 80/443 on your router? There's a chance that will fix the issue, or using a macvlan network interface (as shown in the tutorial) will fix it as well.
@@WunderTechTutorials i forwarded the ports 80 and 443 on my router to 2 different ports on the NAS which in this case is the host and from the Host i bind these 2 ports to port 80 and 443 of the container but still i get an internal error. I did the same with Linux SWAG which is the old letsencrypt i forward port 80 and 443 on the router to 2 other ports on the NAS and from there i bind them to the Linux SWAG container. That worked. i didn't know that i can connect the router port to more than one port on the NAS. What exactly does the macvlan do? and do i also need to add the container to a bridged network? I only created a bridge network for the SWAG container and it worked. However!! because i forwarded port 80 and port 443 to the SWAG container, i think that letsencrypt on my Synology won't work
In summary, it runs containers (which are basically services) in a controlled and resource-friendly manner. Very helpful for a lot of different things.
I just tryit to do macvlan and i got a brain fart i do not understand a single thing, i do not understand what you are doing and im not getting a step further, if anything this exposes the problem that Synology really needs to allow this thru the interface instead
This video is a nice primer to using Docker on a Synology NAS. Thanks for making it!
Superb video... well researched, concise and easy to listen to. Packed with useful info. It consolidated a lot of vague knowledge I had around Docker, Synology's Docker UI and docker-compose. I suspect it won't be the last time I watch this. Small suggestion... you may want to lower your screen resolution (or up the scaling factorto 125%) while recording. Some screens had tiny text.
I appreciate the feedback and will definitely keep it in mind! Thank you for watching!
Thank you soo much. This covers all the basics I've needed to know for years. Every tutorial I've used for installing stuff on my Synology does nothing to describe what Docker is and how it works. And every Docker tutorial is way too in-depth with the software development side of things.
I'm glad it helped!
Just getting into Docker on my NAS atm, trying to set up a 7 Days to Die dedicated server for myself and some mates - Thanks for the tutorial.
I must repeat the other posts. Have been really struggling to get a basis sense of how this works. You explain it perfectly. Thanks so much for that!
The best explanation of this configuration I've come across. Thanks, dude! Liked and subscribed.
Very professional explanation. I learned everything for creating a Pi-hole
Thanks for the kind words!
Great tutorial, pace, voice 👍 thanks
I wish I had watched this before trying to experiment my way through a working macvlan network so that I can reverse proxies on port 443 and then have the proxy be able to communicate to other containers as well as process on the host. I did manage to figure it out eventually myself but your video spells it out so clearly and concisely. Thanks a lot.
Thanks for the tutorial.
Great explanation, thank you.
Thanks so much!
Great content, Thank you!
Great video, great Channel. Nice, slow and good to understand. love it. Greetings from Germany!
Thanks so much! I appreciate the kind words!
Is this as basic as it gets? i am trying to install Xteve in docker but i feel lost.
It is as basic as I can explain it, but from looking up the container you're trying to implement, it doesn't appear to be the most straight-forward. You might have to consult the documentation and really try and break it down and then go from there.
@@WunderTechTutorials thanks, after a lot of trial and error got it working thanks, your explanation for a lamen like me worked! Thanks
Is there a web site that has a list of available containers with descriptions of what they do?
Not the easiest to find new containers, but this is a great repository: hub.docker.com/
@@WunderTechTutorials lol, you're right. I'll just wait until you post a new video as you always come through.
Great stuff as usual, really enjoying the quality content you are putting out!
Thank you so much!!
Sir, the how to use docker-compose on Synology explanation was exactly what I was looking for. Thanks for that. Keep it up!
I'm glad it was helpful, thank you for watching!
Oh thank god, I finally understand, thank you. The only piece of the puzzle missing now is how to run something in docker if it's not in a repository. Like say I have a .jar I want to run, would I have to create my own image with it? How do you make an image?
You can add an image from a file (in the Docker GUI). As far as making that image - I'm not sure unfortunately. I haven't created any of my own Docker containers :-(
I wouldn’t mind a tutorial on how to update docker compose
I will definitely add this to my future tutorials. Thank you for watching!
Dont know if anyone cares but if you're stoned like me during the covid times then you can watch all of the latest movies on Instaflixxer. I've been watching with my girlfriend for the last weeks :)
@Alvaro Porter yea, have been using InstaFlixxer for months myself =)
This video is awesome. I do have a question what if there is no file or page that shows what volumes there are and how do you go about configuring it. I have a come across several docker images that didn't have this information.
Thanks! Some containers don't have volume mounts, but the ones with user data normally do. I don't think there's a way to find it after the download - you might just have to see if you can find it online unfortunately.
Thanks, I got some containers setup with the macvlan method. I can access them all locally but when connected to my network with either OpenVPN or Wireguard, I can't connect to the containers made with this method. Any help would be great!
How are you trying to access them, by IP address? Also, if you are - can you try and access them using the bridge IP address created alongside the macvlan network interface?
Great job. Can you explain how to update a container in synology docker please. Thanks again for this tutorial
Thank you! I planned on creating a separate tutorial for this, but I will give you a brief overview now.
Generally, the easiest way that I find to do it is to download the latest image, stop the container and then right-click it and duplicate settings. It will then create a new container with the same settings (and new image) where you can start it up and test to make sure everything is still working as expected. If it is, feel free to delete the old container.
People have suggested that you can do it by "clearing" the existing container, but that does NOT work for me. I lose all my settings that way. I specifically left this out of the tutorial as I wanted to test this out further, so I will have a tutorial for it at some point!
Feel like I need a video just on Docker-Compose. Installing it, updating it, and how to create the yml files. Amazing content though!
I will keep this in mind moving forward and hopefully create a tutorial for it soon! Thank you!
as stated this is prolly the best explanation.. tho what i dont get if this made for synology why is it made so have to do stuff like mounting configuration etc... synology's credo is/was to keep it simple as possible we should only have to see yes and no buttons and the rest should be done by scripts and auto installs.
(edit) Gave up allready could understand what i did and could not acces the web gui to get to qbittorrent.
I don't use qbittorrent so I can't comment, but the volumes are only necessary to preserve your files (so you can transfer them to a different device if necessary). You can create most containers without any volume mapping.
I would very much appreciate if you could make a tutorial to setup orthanc server inside docker using synology nas
I'll look into it!
Quality video, thank you. How do you destroy/uninstall a container in case you made a mistake and want to remount/compose it from scratch?
Thanks! You can simply go ahead and delete the container in Synology DSM.
New to your channel. Great content
Thanks so much!
Excellent video thanks for breakdown
Thanks so much!
Well what if I cant find docker?
What NAS device do you have?
Thank you for your great sharing! Wondering if you will consider doing a synology NAS and perforce setup tutorial?
Thanks and will definitely add it to my list!
i'm stuck on creating the folder - when i add docker/twonky/config as file/folder, when i try to enter /config as the mount path i get the error "some of your settings are invalid, please enter them again" i can access the folder (docker/twonky/config) from filestation no problem. Any help would be appreciated!
Is the error being reported in the container setup? Are you adding any spaces or anything in the mount path?
Thanks, this was what I need to know
I cant find Docker in my Package Center, do you know why that could be? Im using the DS214play
Unfortunately, Docker is not supported on the DS214Play 😞
I’m going to have to watch this several time to understand how to use docker
I’ve just got my first synology nas ds920+ and I’m a complete noob
I want Sonarr radarr and SABnzbd in docker and to replace Plex and put that in docker 😩😩 I have so much to learn about synology nas’s and how they run
It's a lot to learn, but if you take it slow, you will hopefully understand everything. Not necessarily only from my videos, but there are tons of great videos on these topics. Once it "clicks", it's pretty easy to understand!
Hi i have a DS120j and i cannot install Docker, is this model not big enough ?
I'm not sure of the technical reason, but I don't think that any of the j models support Docker.
I'm confused about some basics. Are we mounting filepaths on the HDDs or is this limited to mounting filepaths on the NAS internal storage?
The hard drives are linked to a storage pool and volume, so while you aren't linking them directly to the HDD, you're linking them to a file path which is part of a volume, which is part of a storage pool, which consists of HDDs. Hope that makes sense.
Thanks so much!
Thank you and quick question. If you create a container with docker compose will it appear in the GUI or is it invisible to DSM? If it is invisible is there a way to add it post deployment? Having the utilization visible of the containers is nice in order to see how your environment is performing and diagnosis of any future performance issues.
It will appear (you might have to logout and log back in), but you can only start/stop the container from the GUI, I believe. You should also be able to see the utilization. If you need to make any actual changes to it, you will have to edit the docker compose file and then recreate the container.
Thank you
How about shared folder permissions for this container?
It will depend on the shared folder.
Hi, the volumes that have been created can be backed up and be restored with hyper backup in case of a system failure?
Or is there a better way?
That is correct! Video coming on out Thursday about this topic 🙂
@@WunderTechTutorials I'll leave a sub then.
The weird backup situation is what currently holds me back from setting it up. Why isn't there a simple "Backup" button on the UI which also let's you restore is beyond me. I know you can export the json, but apparently not Import it....
@@aliasname5518 Generally, Docker containers are meant to be portable, so you don't back up the container, you only back up the important data inside of that container.
Hi Frank,
i don't have a NAS yet, so this might be an obvious question to some. Actually, i'm undergoing the process of understanding Docker, what it is and does, pros and cons and so forth. I understand it now from a developers (which i am not) perspective, but i often read about people running (not developing) applications in Docker, for example on their NAS. Can you help me understand why? Is it because you're not able to install any program you like on a NAS (Is there something like an 'app store')? If not, why not just install the applications on the NAS instead of running them in Docker? What are the pros and cons? I tried finding your emal so i could write you, but with no luck. Hope to hear from you! :)
runs on a smaller footprint, a dockercontainer is really small and only contains what it needs so it doesnt waste resources
(which can be precious in a smaller nas with a weaker cpu+ram combo)
why i use docker: i can run more services with docker on my weak small mini-pc.
There was a great response to this already, but I will add my two cents:
Not all applications that you can run on Docker are supported packages on your NAS. That alone is one of the main reasons that people run Docker containers. Outside of that, you also have portability, so if you ever purchase a home server or simply want to run your Docker containers on a separate device, you copy the data, migrate the containers and everything will function as it did on your NAS. Finally, there are performance benefits (not that I think you'll run into any issues running the packages) as these are lightweight containers that don't take up many resources.
Docker is AWESOME, and it's something you should definitely check out, but outside of a few specific scenarios, you'd basically be installing the same exact application as the package (assuming there is one), which makes this mostly a personal preference.
@@siriuswinter1065 Thank you!
@@WunderTechTutorials Thank you so much for your answer, also to @Sirius, that made a lot of sense!
9:15 this would not be an issue if docker had macvlan configured per container
the docker package isn't available in my package center.... how to procede?
Unfortunately, your device most likely doesn't support Docker 😞
I wish I new how to use Falcon Christmas FPP on docker. Installed it many time but have no idea how to use it.
Never heard of it. I'll look into it!
@@WunderTechTutorials Perfect thanks, installing docker and installing the image in docker isn't a problem. Once I run it, I'm assuming it should show up on my router with an IP Address but it never does.
@@Victork32 That is correct - if it's not getting an IP address, something is off. Could be a port conflict or it could be a more involved setup (which some containers need).
I wish the docs on the pi-hole website were as clear as this
I'm glad the info helped! Thank you very much for your donation!
I cant find docker in the store or anywhere on my nas =/
I have DS413 and do not find docker when I search package center
I unfortunately don't think the DS413 supports Docker :-(
Hey Wunder, we're trying to install Mattermost via Docker on Synology. We followed your tutorial (really appreciate it) and got it all set up, but once we start the container it keeps getting our the same error every few seconds: Error: failed to load configuration: could not create config file: open /mattermost/config/config.json: permission denied. Why is this happening? We tried giving High privilege, but the result is the same. Any tips how to fix this? Thank you.
It could be a permission issue even though the container has high privilege. Have you created the config.json file? Played around with any permissions?
@@WunderTechTutorials thanks for the reply. No, I haven't created the config.json file. Do I have to create one? No official Mattermost guide says this, and since I'm fairly new to Docker use I might be wrong and it might be a basic thing that is not even mentioned in the guides. I even tried to fix it by creating a new user with read/write permission to docker, found his uid and gid through putty and set it under the Environment variables of the container. I tried disabling the firewall, thinking that it's maybe the culprit in this case (though that might not have anything to do with it), but the error persisted. What could be the cause?
@@RedMartyrEntertainment I can't say for sure as I haven't ever created a Mattermost container, but a lot of times, config.json files include some sort of database configuration. If it does, you're most likely better off trying to use Docker Compose through the terminal than Synology's GUI. Might just be easier that way.
All i need is customizable dhcp server that can set efi and pxe bootloaders at same time and all i get is pain
the workaround with macvlan did not work - ports still being blocked (as error when try to start the container by console) - weirdly enough, the docker container got the same ip as the host, but i can ping outside the container, which is half of a success
When you created the container, did you remove the bridge network and assign the macvlan?
When I try to download a new image I kept getting timeout. I tried changing my DNS to use cloudflare but still have the same timeout issue and cant download any new images. Do you have any idea on why this occurs and how I can fix it?
That definitely sounds like a DNS issue if it's happening to all images. Can you try changing the DNS back to what it was?
@@WunderTechTutorials I already tried but to no avail
@@jimmycoconut88 I haven't seen it happen in a scenario where it wasn't DNS related. I would try and isolate what else isn't working (as other things most likely aren't working either, you just haven't come across them yet).
Great video, nice job! I'm experiencing issues with docker on the Synology NAS, I'm trying to run a container for my Tesla. Runs fine on RPI but issues on the NAS. Still investigating the issue. Anyon running Teslamate on the NAS?
Are you receiving any errors when you run it? Anything different from the RPi?
Dang! This was a great intro. I couldn't figure out anything after pulled the Valheim docker.Thank you.
Glad that it helped!
G'Day and thanks so much for this great Tutorial. I just bought a Synology NAS and am brand new to Docker. This was invaluable. I'm now about to watch your tut on Docker Compose. Cheers.
I'm glad that it helped, thanks so much for the kind words!
This is great. I have an issue I'm trying to solve and would love to see if you have an easy solution.
Using HAProxy I want to run a reverse proxy on the Synology NAS. Seems simple. I found a command to unbind 80 and 443 from the Synology server but I get a "cannot bind socket (permission denied)" error when I run up the HAProxy Docker container. What I think I need to do is run the "--sysctl net.ipv4.ip_unprivileged_port_start=0" flag but I don't know how to add this on a Synology server or if I can.
Hmm, if you're using HAProxy, any reason why you want to unbind 80/443 from the NAS? You should be able to set up the source as 443 and the destination (on your local network) as the DSM port.
@@WunderTechTutorials I'm confused by your reply.
HAProxy is being used for reverse proxy.
443 is the standard port for https. in HAProxy (docker container) we have mapped it to 4443 but in docker in the translation table when we try to make that port 443 so there is no need to type a port into a browser (a UX pain) it won't let us. We just want to get a workaround for that part of the process. everything else seems to be working now.
basic set-up; one customer-facing access to two microservices. all over HTTPS.
@@chrisschneider7609 My question is more on the Synology side as to why you're trying to unbind ports 80/443 on the NAS? I am assuming that you have HAProxy running on a difference device, so you should be able to leave the DSM port as 5001 (or something different, just not 80/443), and use port 443 on the HAProxy side without adjusting DSM at all.
@@WunderTechTutorials No, I'm trying to run HAProxy in a docker container... Hence the question.
@@chrisschneider7609 I would look into using a macvlan network interface for it then. I'm not a fan of unbinding 80/443, but ultimately, it's up to you.
What model Synology NAS do you use? ty
Currently using a DS1019+, but any "+" model will support Docker.
Is there a way to setup more then one macvlan ?
nvm found it just do same command without --ip-range= filled in and it will use everything
Sorry for not getting to any of your questions in time, but glad you got it working!
I finally had it working but then i get error only to find out i used wrong adapter and now i cant add a new one, how do i remove it ? or am i fucked and forced to wipe my entire 14 tb nas just to fix one mistake ?
I have installed Nginx reverse proxy manager as a docker container on my Synology but if i request a certificate from Let's encrypt i get an internal error. I suspect that it has something to do with the port configuration. Since i work on a NAS where my Docker is installed I can't use port 80 and 443 for Nginx directly. i had to forward them with different port numbers on the Host. I think i can solve it if i connect the container to a different network. You think that's a good idea and what should i do?
I have a tutorial up for Nginx Proxy Manager in specific. Some people have issues with it, but you're correct in stating that it's probably port 80/443. Have you port forwarded the ports you mapped to 80/443 on your router? There's a chance that will fix the issue, or using a macvlan network interface (as shown in the tutorial) will fix it as well.
@@WunderTechTutorials i forwarded the ports 80 and 443 on my router to 2 different ports on the NAS which in this case is the host and from the Host i bind these 2 ports to port 80 and 443 of the container but still i get an internal error. I did the same with Linux SWAG which is the old letsencrypt i forward port 80 and 443 on the router to 2 other ports on the NAS and from there i bind them to the Linux SWAG container. That worked. i didn't know that i can connect the router port to more than one port on the NAS. What exactly does the macvlan do? and do i also need to add the container to a bridged network? I only created a bridge network for the SWAG container and it worked. However!! because i forwarded port 80 and port 443 to the SWAG container, i think that letsencrypt on my Synology won't work
sorry. not working
message":"failed to create the macvlan port: device or resource busy
Did you select the correct network interface name (from your NAS)?
@@WunderTechTutorials sorry yes, I forgot that I have ports in aggregation, changed eth0 to bond0
I watch this video as a Hail Mary to why my Pihole stopped working after a Synology upgrade. Network mapping changes. THANK YOU 🙏🏻 subbed
Glad to hear it helped! Thanks for the support!
how to update Docker 18.09.0-0513 in synology
Unfortunately, you will have to wait for Synology to do that :-(
my Synology NAS do not have Docker :(
Yeah, unfortunately not all Synology NAS devices support Docker 😞
Ok so now I have a container in my docker how the hell do I use it?
It will depend on whatever container you created. Accessing them is different based on the configuration/port number.
Gee sounds great. But I still don’t know what Docker is or does. 🤣
In summary, it runs containers (which are basically services) in a controlled and resource-friendly manner. Very helpful for a lot of different things.
I just tryit to do macvlan and i got a brain fart i do not understand a single thing, i do not understand what you are doing and im not getting a step further, if anything this exposes the problem that Synology really needs to allow this thru the interface instead
I feel 1 like wasn't enough.
Thanks so much!
Wow, way out of my depth here.
If there's anything I can answer to help, let me know!
Me too. Nothing has made me feel so stupid as trying to make sense of Docker and even my Synology DS920+
Thanks for the tutorial. RS3614xs+ here
I'm using DS1817 but I couldn't find docker in package center
Hmm, I believe that the DS1817 supports Docker. Are you on DSM 6 or 7?
@@WunderTechTutorials Hey thanks for replying. I'm on version 6.2.3-25426 Update 3. I guess I have to update to 7?
@@WunderTechTutorials Edit1 : I have updated to DSM 7 but docker is still not showing..
@@waitiwanttopee I apologize, I was under the impression that the 1817 was the 1817+. I don't believe docker is supported on the 1817.