Overview: Container execution
Container execution connects packaged software with mapped storage, process isolation and shared resource controls.
An image, a running container and a persistent volume have different lifetimes. Bind mounts define path relationships, while resource limits constrain work within the host environment. These topics explain how a replacement container can reach the intended Emby data without assuming that its image contains the previous server state.
Software containers
A software container gives a process an isolated view of selected resources while using the kernel supplied by its execution environment.Docker images and containers
A Docker image supplies a packaged filesystem and configuration, while a container adds a running lifecycle and a writable layer.Container bind mounts
A container bind mount exposes a selected daemon-host path at a container path, with the source tree and process identity still determining access.Container volumes
A container volume stores data outside one container's writable layer, with a managed identity and lifecycle that require deliberate reuse and backup.Container resource limits
Container resource controls bound or prioritize a workload's CPU and memory use within a shared host rather than creating dedicated hardware.