The writable layer belongs to one container. A named volume has a separate lifecycle, which lets data survive container replacement. A bind mount exposes a specific host path inside the container. Choose the source based on who owns the data and where it must persist, then choose the target the application expects. The target path can hide files already present in the image. A read-only mount prevents container writes through that mount, which suits preview content managed on the host. The tasks distinguish persistent application data from host-maintained pages and check the mount type as well as its path.