Post #1810090

2026-04-30 14:29 UTC

@k4t3@comp.lain.la docker compose is more fun and building your own Dockerfile can be fun but also sometimes a hassle too

Replies (2)

@7666@comp.lain.la 2026-04-30 14:40

@voidplush@dorm.social @k4t3@comp.lain.la do not use docker and fun in the same sentence ever again

Open ##1810861
@k4t3@comp.lain.la 2026-04-30 15:20

@voidplush@dorm.social You're tying your build logic into a DSL that has: - no proper conditionals (you're stuck writing shell-conditionals) - no proper dependency graph (or rather: good tooling to examine it) - no real caching semantics (basically you rebuild _everything_ below a changed line?) Even at as few as ~10 services, this starts to begin being a real problem, to a point where you're either 1. basically clean-rebuilding everything after each small change or 2. maintaining a second environment, seperate to your docker-env where you're doing development on, running into small surprises each time they go "out of sync". this gets progressively worse the more intertwined your services are. rule of thumb: the moment you start writing a script to manage your dockerfiles is the same moment you should stop and move to a real large scale build system.

Open ##1811237