4 ms·

Right glibc does, but with containers this isn't really an issue for getting it to work, just include the correct version of the deps. The issue is security at

Right glibc does, but with containers this isn't really an issue for getting it to work, just include the correct version of the deps. The issue is security at that point though as it's unsupported software now. The libraries going up do to. And again, these are expert friendly features at this point, I think. I don't know of any software to make old linux software work.

PaulHoule 2y ago
I know my case is unusual but I've had terrible experiences with containers. Back when I had 2 Mbps DSL I frequently downloaded multi-GB files, I just used download managers and waited. I could never get anything to work with Docker back then because Docker Hub was unreliable, so consistently reliable that it probably had some timeout that made it impossible to use with a slow connection. I guess reliability is a "call sales" kind of feature for Docker. I have 10x the speed now, but when I wanted to try the Danbooru image board software locally I was told to use "docker compose" which didn't work because I had the wrong version of compose. Maybe I could switch back to an old version of compose, but would that break some other container thing running on my server that I don't know about? Maybe I could update the compose file to a new version but really it seemed better to hack my RSS reader into an image sorter than go down that rabbit hole. At one place I worked management thought Docker was an answer to the Python morass but all I saw it do was speed up the ability of the data sci's to find unimaginably broken Python distributions. Docker lets you run 20 microservices that depend on 20 different versions of their environment but in the end now you have to deal with 20 different versions of the environment. Docker alone is chaos, docker + discipline is OK, but the discipline without Docker is also OK. It's the discipline that matters.
- beached_whale 2y ago
  I think debian publishes their rootfs build docs. But, that's kind of my point on it only really being expert friendly right now. Maybe it's easier to make a flatpak or snap, but I don't know.

PaulHoule 2y ago

I know my case is unusual but I've had terrible experiences with containers. Back when I had 2 Mbps DSL I frequently downloaded multi-GB files, I just used download managers and waited. I could never get anything to work with Docker back then because Docker Hub was unreliable, so consistently reliable that it probably had some timeout that made it impossible to use with a slow connection. I guess reliability is a "call sales" kind of feature for Docker. I have 10x the speed now, but when I wanted to try the Danbooru image board software locally I was told to use "docker compose" which didn't work because I had the wrong version of compose. Maybe I could switch back to an old version of compose, but would that break some other container thing running on my server that I don't know about? Maybe I could update the compose file to a new version but really it seemed better to hack my RSS reader into an image sorter than go down that rabbit hole. At one place I worked management thought Docker was an answer to the Python morass but all I saw it do was speed up the ability of the data sci's to find unimaginably broken Python distributions. Docker lets you run 20 microservices that depend on 20 different versions of their environment but in the end now you have to deal with 20 different versions of the environment. Docker alone is chaos, docker + discipline is OK, but the discipline without Docker is also OK. It's the discipline that matters.

beached_whale 2y ago
I think debian publishes their rootfs build docs. But, that's kind of my point on it only really being expert friendly right now. Maybe it's easier to make a flatpak or snap, but I don't know.