3 ms·
Because building a sane filesystem with only the needed libraries needs knowledge and some effort, whereas containers exist to keep people from using their brai
by snickerer 3y ago
Because building a sane filesystem with only the needed libraries needs knowledge and some effort, whereas containers exist to keep people from using their brains.
If you know what you are doing you have several alternatives:
1. Just link your binary statically.
2. Set the path to the picked out special libs as an environment variable only for the binary.
3. Re-think what's wrong with your system that leads to the pain of you wanting other lib versions for that binary.
- tracker1 3y ago1. Statically linking your application, then distributing that application, such as via Docker Hub to others will then require your application to be GPL licensed in many, many cases within the Linux ecosystem. This may not be desired. 2. You can absolutely limit the system libraries that are included to only those needed. Some platforms make this easier or harder than others. 3. That you have other software that you want to run in parallel and don't want to spin up full virtualization or manage various chroot structures to organize. I'd also add that just because a tool makes it easy to do something, and means you can bloat your file system doesn't make it inherently bad. Not everyone is trying to run a large database on a potato.