4 ms·
>Doing anything non-default with networks in Docker Compose will often create stacks that don't work correctly on machines with complex network setups. I run i
by ycombinatrix 3y ago
>Doing anything non-default with networks in Docker Compose will often create stacks that don't work correctly on machines with complex network setups.
I run into this often. Docker networking is a mess.
- j45 3y agoDepending on the load and use case, encapsulating docker itself in an lxc container or a standalone vm can be a semi maintainable and separated solution.
- heatmiser 3y agoI like this approach for running multiple services on customer servers/clouds. for my own cloud though, i'll use some orchestrator that makes sense
- j45 3y agoThanks. I'd be interested to learn what direction your orchestrator search goes in. My thought usually is how to make any environment the equivalent of an appliance and require as little upkeep as possible. I have been contemplating how Terraform may be able to sit in a private/hybrid cloud design, but haven't looked into it much.
- NorwegianDude 3y agoDocker in lxc is also a huge mess when it comes to storage drivers with some backends...
- j45 3y agoI appreciate the heads up on this in case I run into it. If you have any examples of what to look out for it would be great to know if it hits my use case
- kobalsky 3y agoyou are not using podman right? the only implementation to give me headaches on the networking side
- ycombinatrix 3y agono, not using podman. i hear podman has performance issues with shared tmpfs volumes.