[techdragon]

Docker compose files have been treated like legacy technical debt in a lot of places and the availability of tools to easily convert them, has lead to the current situation where basically I only see new docker compose files used by themselves in hobby and amateur projects with any reasonably organised project making the jump to at least publishing both the compose AND the helm chart or kompose template driven kubernetes configuration files… the hobbyist use i have not qualms with, use what you want to use for your own stuff, but a large portion of the use of docker compose in this particular NAS as host ecosystem is using shared application deployment configurations to make it easy to start up things like Plex or qtorrent or NextCloud. These are organised efforts where people post files to indexes to make them easier for others to find, and the greater rigour of a kubernetes config is actually a good thing in this environment… but it’s more work and a lot of the time I have seen the kind of complaints the users make and the bar to entry is very low for these things… I remember when the only way used to be templated FreeBSD jails… and now they are telling the company a kubernetes config is too hard… I don’t care what they want to use in their own home lab, I care about how hard it is to fix when their poorly written docker compose file breaks… how hard it is to maintain my system security now that we’ve thrown out the more comprehensively documented security architecture of kubernetes for the docker compose world with a much less rigorous security story…

This is a step back and the users are in this case wrong to have wanted it. I’m expressing the same sentiment you might have if you found someone was lighting their house with whale oil powered lanterns for the last year… it’s not that it doesn’t light the house… it’s just a very damn strange way to light a house in the 21st century.