That’s my theory admittedly based on not much actually. It has to load those shared libraries itself. Since the container is running in its own cgroup it doesn’t have access to the already shared libraries from the host or any of the other containers. My ancient and half remembered understanding is that shared libraries get loaded by the kernel once and the kernel manages access to them from the different processes. I agree, it’s not fully virtualized but I wonder if the OS is no longer able to share libraries between different processes when they are running in the same kernel namespace.
I’ve never really looked into it that deeply but that is my experience.
Is this the case? Docker applications are not actually virtualized, unless run on a non native platform (like using linux on virtual box on a mac).
