shared library
Ready-made code that many programs load at run time instead of each carrying its own copy.
In more detail
On Linux they are .so files, such as the C library, that programs load when they start. Upgrading a shared library updates every program that uses it at once, but a version different from the one a program expects can make it fail. Container images and statically linked programs avoid this by carrying the exact libraries they need.
Example
On Windows, shared libraries are DLL files.Related terms
- dependency — Anything a program needs in order to work, such as a library, a tool or another service.
- configuration drift — The slow, unrecorded way machines end up with different versions and settings from each other.
- image — A read-only package containing a program and everything it needs to run, used as the template for containers.
- language runtime — The software a programming language needs installed to run programs, such as the Python interpreter or Node.js.
- software package — An archive containing a program's files plus metadata: its name, version, dependencies and scripts to run on install or removal.
- executable — A file the operating system can load and run as a program, such as a compiled binary or a script with execute permission.
Taught in
- Why Containers: Bare Metal, Machines And Processes — Docker Architecture & Production Containers
- Pull And Inspect A Third Party Image — Docker Architecture & Production Containers
- Installing the Go Toolchain — Concurrent Systems Programming with Go
- Go Workspaces and Modules — Concurrent Systems Programming with Go
- Building Static Binaries — Concurrent Systems Programming with Go
- What A Kernel Does, And What It Refuses To Do — Linux Fundamentals & Systems Administration
- What A Package Manager Guarantees — Linux Fundamentals & Systems Administration
- Memory Forensics: Process Trees & Injection — Security Operations & Threat Hunting (SOC)