You're right that I'm not too familiar with Docker containers lol. I know the basics of how they work but in terms of how it communicates with anything network related, I'm not that experienced with.
Ah okay that actually sense. Using the analogy of Docker behaving as a router simplifies things a lot. Each container has their own internal address inside of a stack and if you want to communicate between stacks (containers outside of local stack scope), you'd have to use a proxy that encompasses both stacks.
And yes, Velocity can run inside of a container and good to know that I don't have to set up the minecraft containers with external ports. But that would only be possible if they were all inside the same stack (which you have outlined in your diagram).
And you also mentioned I could theoretically run Velocity on another computer (another Pi in this case) which implies that containers from different machines on my local network can be on the same stack (I assume). I probably won't as Velocity isn't too resource intensive (it's actually a performance-optimized fork of another minecraft proxy software, BungeeCord).
Lastly, you mentioned that Docker acts a firewall to containers & stacks running inside of it and your first velocity diagram points traffic directly to the Docker stack. I have a firewall on my Pi (UFW) so I would only need to open up the velocity container then presumably.
And thank you for the detailed explanation, really appreciate it!
Ah okay that actually sense. Using the analogy of Docker behaving as a router simplifies things a lot. Each container has their own internal address inside of a stack and if you want to communicate between stacks (containers outside of local stack scope), you'd have to use a proxy that encompasses both stacks.
And yes, Velocity can run inside of a container and good to know that I don't have to set up the minecraft containers with external ports. But that would only be possible if they were all inside the same stack (which you have outlined in your diagram).
And you also mentioned I could theoretically run Velocity on another computer (another Pi in this case) which implies that containers from different machines on my local network can be on the same stack (I assume). I probably won't as Velocity isn't too resource intensive (it's actually a performance-optimized fork of another minecraft proxy software, BungeeCord).
Lastly, you mentioned that Docker acts a firewall to containers & stacks running inside of it and your first velocity diagram points traffic directly to the Docker stack. I have a firewall on my Pi (UFW) so I would only need to open up the velocity container then presumably.
And thank you for the detailed explanation, really appreciate it!
Statistics: Posted by ethanic — Fri Aug 23, 2024 8:55 pm