How does the use of dynamic libraries (shared objects) work in a container?
Linux - ContainersThis forum is for the discussion of all topics relating to Linux containers. Docker, LXC, LXD, runC, containerd, CoreOS, Kubernetes, Mesos, rkt, and all other Linux container platforms are welcome.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
How does the use of dynamic libraries (shared objects) work in a container?
Hello, I'm starting studies with container.
I would like to understand how the use of dynamic libraries (shared objects) of the docker works. When the container runs an Ubuntu image equivalent to the host machine's version, will it use the same libraries? Is there any way to capture the libraries used by a specific container?
Some containers are built to expose access to the host system's library directories through the use of controlled links. Others are built to put copies of the libraries that are needed by the container directly in a filesystem that is particular to that container ... so that the container's definition is self-contained. You can do it either way.
In either case, "the container's occupants see only the perfect illusion that you have created for them." They perceive a "file system" that contains exactly what you've put there, and they have no idea where its contents actually come from. (Nor do they [have to ...] care.) They do not see the host at all – only the illusion, which is enough.
Last edited by sundialsvcs; 10-08-2021 at 02:51 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.