Volumes — by Docker Docs

intermediatepageLink only (©)

Docs on persisting container data with volumes, which Docker calls the preferred mechanism, versus bind mounts that tie you to the host's folder layout. Mentions read-only mounts, subdirectory mounts, volume drivers for NFS/CIFS, and the gotcha that mounting over a non-empty directory hides its existing files. Volumes are not removed automatically when a container is deleted.

Quick steps

Use --mount rather than --volume when you need driver options or subpaths
Clean up unused volumes with docker volume prune

Paraphrased from the source. Menus can differ by version, so check the original for full details.

Read the full article on docs.docker.com

Source: Volumes by Docker Docs. Licence: Link only (©).

Source reviewed: 2026-11-02
Link checked: 2026-11-02
Tested hands-on: Not by Oddbyte.Me

dockervolumesbind mountsstorage

More in Docker & Containers

Docker Compose Quickstart — by Docker Docs

beginnerpage

A hands-on tutorial that builds a small Flask app with a Redis counter and runs it with a compose.yaml. It covers health checks, Compose Watch for live updates, persisting data in a named volume, splitting config files and inspecting a running stack with logs and exec.

Install Docker Engine on Ubuntu — by Docker Docs

beginnerpage

Official install guide using Docker's apt repository, which installs the engine, CLI, containerd, buildx and compose plugins. It warns that with ufw or firewalld, published container ports bypass your firewall rules, and that Docker only supports iptables-nft and iptables-legacy.

Docker image/container upgrade best practise — by ahokanson, meyay and goffinf on Docker Community Forums

intermediateforum

A discussion of how to update a container when its image changes. Answers say to stop the old container first if ports are exposed, manage containers with Compose, rebuild with --no-cache --pull for evergreen tags, and that reusing the same tag breaks image immutability, so explicit version tags are preferred.