Comment on My Overconfidence Killed Me and My Immich Installation
sabreW4K3@lazysoci.al 2 months agoThank you very much. I had one eye on combining all my compose files in the future to make things more remotely manageable and that’s probably been my folly here.
lemmyvore@feddit.nl 2 months ago
It’s good to want to have that but dumping everything in one compose file is not the way. Read through the compose docs, there are many things you can use to achieve modularity. Start with fragments then continue with the next sections (extensions, interpolation, merge, include and profiles).
If you want to do things with networking you can, there’s a ton of things you can do to make containers connect in all kinds of networks, you can control IPs, you can control MACs, you can make containers show up as regular machines on your LAN and take their IP from DHCP and have names in DNS etc.
The only reason to put things in the same compose file is as a convenience when you have a set of containers that are strongly related and make up a single “app” between them, but some applications go overboard with complexity. Immich is merely mildly annoying, have a look at mailcow for comparison, now that’s bad.
sabreW4K3@lazysoci.al 2 months ago
I’m not going to lie to you, clicking that second link was overwhelming, but that first link… that made me grin like a child that just got a bag of sweets. Thank you!
lemmyvore@feddit.nl 2 months ago
It’s worth reading through all the docker docs sometime, it can do a lot of cool stuff. I’ll leave these here:
The mailcow compose is actually worth coming back to when you’ve had some more experience. There are a ton of interesting tricks in there like overriding the DNS server, defining fallback values for env vars, sharing/unsharing volumes between containers with the
:zand:Zflags, [ab]using thecommandto perform initializations or to wait for another container etc.