The internet says "containers are the holy grail, it's cross-platform and you can run your images and get the same result everywhere"

The practice says: nope... it doesn't do that

My favourite is when different instruction sets break things in different ways...

@atheist I haven't been bitten by diff instruction sets in containers yet. Care to elaborate?

If you get bored by Docker, try NixOS

@usr--2ndry I'm struggling to find package versions' archives in the search webpage

@netikras the classic is when something just straight up crashes because some dependency doesn't support the instruction set on a slightly older server, but it takes ages to work that out. Or different instruction sets mean a slightly different computed result, failing some regression test and spending hours working out why because something was compiled with funsafemath

I hate how the providers of software can just be lazy and tell you to install it on docker

instead of updating their damned software so it works on modern systems

cuz if I touch fucking anything in the docker everything breaks. if I don't have the exact same use-cases hey guess what the devs don't care just use docker in the one approved way we envisioned it to be used

so fragile

If all components of your app run natively on your os, you don't need containers.

@kiki you do when it means conflicts (lib/ver) with other apps.

@netikras we have a billion solutions to this: versioned lib files, chroot, recompiling from source, switching programs and not putting up with that shit... you have options that aren't "run virtualbox with a shared folder tied to the host's root" for every single program.