Live data from Hacker News

Should I run plain Docker Compose in production in 2026?

distr.sh

311–312 of 312 posts

Re: Should I run plain Docker Compose in production in 2026?

#311

Just use nix flakes

Well yes, but if you think you need docker-compose then you're looking for runtime control and not build time control, so you should use this nix flake: https://github.com/juspay/services-flake (which uses process-compose instead of docker-compose).

I appreciate you sharing this with me!

Re: Should I run plain Docker Compose in production in 2026?

#312

Earlier quoted context omitted.

Sure! Get a few Beelink SER5 or SER9's, install Nextcloud to cover the files, document editing, communications (to save on Microsoft 365). Then you can have Gitea (and gitea actions) for your source code and building (skipping github enterprise), Harbor to host and scan your containers, frappe for HR, etc. Pretty much anything you pay enterprise rates for, you can self-host a version that will get your company from 1…

I checked your page. Wanted to ask, are you using longhorn with k3s for replicated volumes? How beefy a box do you need for that (CPU/MEM/Disk speed)? I have several VMs in clouds with similar k3s architecture as yours and am wondering if there are any benefits to installing longhorn vs sticking to logical (postgres, mimir, whateveritis) replication instead.

I am using longhorn because it comes with k3s. It's mostly useless for replication until I get another node, but it's a great storageclass.
Post reply on HN