Docker - Lightbulb

A quick thought

1. When you build your docker network, think about your networks, ie.. backend, frontend, proxy, tunnel etc..
2. Create these in your basestack (so since my base stack is watchtower, clamAV, fail2ban etc..), I would attach all the above to backend-net but then create the additional networks for later use in the same stack.
3. By doing this you have established the base docker networking infrastructure in a controlled manner allowing for later migration, and other rather handy consistencies
4. You then deploy this base stack across your various servers, so everything networking has the same structure.
5. Obviously if you have a service that requires an independent network this can still done.

Problem solved ✅

By the way, I am beginning to hate databases. As you start playing with more complicated and numerous services, you will find the number of databases you need explode. Version control, isolation and resource management becomes an issue. LXC containers rock in regards to resources.

#enoughsaid