Comment by oarsinsync

Comment by oarsinsync 10 months ago

After 20 years of various things breaking on my (admittedly franken) debian installs after each dist-upgrade, and spending days troubleshooting each time, I recently took the plunge and switched all services to docker-compose.

I then booted into a new fresh clean debian environment, mounted my disks, and:

  cd /opt/docker/configs; for i in *; do cd $i; docker-compose up -d; cd ..; done

voila, everything was up and working, and no longer tied to my underlying OS. Now at least I can keep my distro and kernel etc all up to date without worrying about anything else breaking.

Sure, I have a new set of problems, but they feel smaller.

dijksterhuis 10 months ago

Thou hast discovered docker's truest use case.

Like, legit, this is the whole point of docker. Application/service dependencies are no longer tied to the server it is running on, mitigating the worst parts of dependency hell.

Although, in your case, I suppose your tolerance for dependency hell has been quite high ;)

Reply View 1 reply

oarsinsync 10 months ago

> Application/service dependencies are no longer tied to the server it is running on, mitigating the worst parts of dependency hell.
Until you decide to optimise for resources, and do crazy things like “one postgres instance, one influxdb instance” instead of “one instance per microservice”, and then you get back into hell pretty quick.
Winds me up how massive tiny applications become, and how my choices are to throw money (RAM) at the problem, or money (time) at the problem. I wonder when someone will do the math and prove that developer laziness is having a substantial drag on global efficiency. The aggregate cost bourn by users has to be orders of magnitude larger than the cost savings made by developers at this point.

Reply View | 0 replies

aflukasz 10 months ago

> Now at least I can keep my distro and kernel etc all up to date without worrying about anything else breaking.

I get what you are saying, but note a word of caution - kernel upgrades can break container runtimes: https://github.com/containers/podman/issues/10623.

Reply View 0 replies

Ringz 10 months ago

I'm doing exactly the same thing. I started to do everything on Synology with Doctor Compose and got rid of most Synology apps: through open source applications.

At some point I moved individual containers to other machines and they work perfectly. VPS, NUC no matter what.

Reply View 0 replies