| ▲ | johannes1234321 3 hours ago | |
It's not that easy. First I need to monitor all the dependencies inside my containers, which is half a Linux distribution in many cases. Then I have to rebuild and mess with all potential issues if software builds ... Yes, in the happy path it is just a "docker build" which updates stuff from a Linux distro repo and then builds only what is needed, but as soon as the happy path fails this can become really tedious really quickly as all people write their Dockerfiles differently, handle build step differently, use different base Linux distributions, ... I'm a bit surprised this has to be explained in 2025, what field do you work in? | ||
| ▲ | rkomorn 3 hours ago | parent [-] | |
It does feel like one of the side effects of containers is that now, instead of having to worry about dependencies on one host, you have to worry about dependencies for the host (because you can't just ignore security issues on the host) as well as in every container on said host. So you go from having to worry about one image + N services to up-to-N images + N services. | ||