Thank you for your comment. I do really appreciate ! My home lab is simple. no subnets or vlan. I am slowly getting all converted in to property network. One thing with homelab stuff - network is still goes above my head when it comes to setting up all this. So i am doing baby steps to learn, troubleshot and get hang of it before doing full deployment or teaching other.
@@MRPtech You are welcome - I was intrigued looking at the IP Addresses that your docker containers are using - I see some with 192.168.x.2 and some with 172.x.0.2- normally, I would have though that there would be a combination of 192.168.1.x and 172.11.x.2 - are you using wider subnet masks, or am I misunderstanding how it works. As an aside - I note somewhere you have a Synology DS423 - I have a DS918 - have you experimented with Docker on it, and integrating that in any way with your docker cluster? I have a similar config - three NUCs - just rewatching your other video on setting up cluster and storage for the 4th time - have some questions on that, which I am prepping. BTW - I am known as Mr. Q. We must be kindred spirits.. 🙂
Hi Mr Q. These IP addresses you see next to docker containers are internal docker network ip addresses. Its like mini subnets inside your main network. each container gets assigned its own subnet. by default all starts with 172.* but you can change that to any subnet you want (not your local) If you want two containers to talk to each other - they must have same subnet a.k.a be inside same docker network.
Love your tutorials. So detailed and easy to understand. Keep up the great work.
Thank you!
This was superbly presented, thanks!
Love your work, would like to see a how and why on how you have structured your network (subnets etc)
Thank you for your comment. I do really appreciate !
My home lab is simple. no subnets or vlan. I am slowly getting all converted in to property network.
One thing with homelab stuff - network is still goes above my head when it comes to setting up all this. So i am doing baby steps to learn, troubleshot and get hang of it before doing full deployment or teaching other.
@@MRPtech You are welcome - I was intrigued looking at the IP Addresses that your docker containers are using - I see some with 192.168.x.2 and some with 172.x.0.2- normally, I would have though that there would be a combination of 192.168.1.x and 172.11.x.2 - are you using wider subnet masks, or am I misunderstanding how it works.
As an aside - I note somewhere you have a Synology DS423 - I have a DS918 - have you experimented with Docker on it, and integrating that in any way with your docker cluster?
I have a similar config - three NUCs - just rewatching your other video on setting up cluster and storage for the 4th time - have some questions on that, which I am prepping.
BTW - I am known as Mr. Q. We must be kindred spirits.. 🙂
Hi Mr Q.
These IP addresses you see next to docker containers are internal docker network ip addresses.
Its like mini subnets inside your main network. each container gets assigned its own subnet. by default all starts with 172.* but you can change that to any subnet you want (not your local)
If you want two containers to talk to each other - they must have same subnet a.k.a be inside same docker network.
I tried to add syncthing using this guide but I get the error - empty compose file, what am I doing wrong
Is there any way, that it automatically create this stack in portainer with new repository in github my repository.
Thank You.
Nice. Can it be done in reverse easily? From local to GIT? It seems that you have to delete your existing stack and recreate with gitops version.
It doesn't seem to be an option but if you're using persistant volumes, you should be fine to just delete the stack and add a new one.