Yaya data persistence ke aiki tare da Docker volumes?

Question

Accepted Answer

A by default, data a cikin container shine **ephemeral** — an rasa shi lokacin da aka cire container. **Volumes** (da bind mounts) suna ba da **persistent storage** da ke tsaye ko da container ya tashi, abu mai mahimmanci ga databases da kowane data da sai ta tsugunar container restarts/removals.

## Matsalar: containers su ephemeral ne

```text
A container's writable layer is DELETED when the container is removed:
  → data written inside the container (e.g. a database's files) is LOST
  → containers are meant to be disposable/replaceable → don't store important data in them
→ For persistent data, you need storage OUTSIDE the container's lifecycle.
```

## Volumes — managed persistent storage

```bash
# create and use a named volume (managed by Docker)
docker volume create mydata
docker run -v mydata:/var/lib/mysql mysql      # mount the volume into the container
# → data in /var/lib/mysql persists in the volume, surviving container removal

docker volume ls                 # list volumes
docker volume inspect mydata     # details
```

**Volumes** su Docker-managed persistent storage ne (stored a kan host, managed by Docker) — hanya da aka fi so don tsugunta data. Data a cikin mounted path na tsugunar ko da aka cire container.

## Bind mounts — map a host directory

```bash
# bind mount: map a specific HOST directory into the container
docker run -v /host/path:/app -p 3000:3000 myapp
docker run -v $(pwd):/app myapp   # mount the current directory (great for development)
# → changes on the host are reflected in the container (and vice versa)
```

**Bind mounts** suna map host directory zuwa container — abubuwa da ke da amfani don development (gyara code a kan host, ganin changes live a cikin container).

## Volumes vs bind mounts

```text
VOLUMES      → Docker-managed, portable, the preferred choice for PERSISTENT DATA
               (databases, uploads) — decoupled from the host's filesystem layout
BIND MOUNTS  → map a specific host path; great for DEVELOPMENT (live code reload)
               and sharing host files; tied to the host's filesystem
tmpfs        → in-memory (non-persistent), for sensitive/temporary data
```

## Me yasa ya mahalaka

Sanin how data persistence ta aiki tare da volumes abu ne da ya zama dole don amfani da Docker daidai tare da duk wani application da ke da data, saboda haka abu ne mai mahimmanci na aiki.

Abubuwan gida — **containers su ephemeral ne**, tare da kansu writable layer aka cire a cire, ma'anan **data written a ciki container ana rasa shi** — abubuwa ne na mahimmanci: containers an yi musu saboda su zama disposable, don haka storing data mai mahimmanci a ciki su (kamar files na database) kan butsa data sa'ad da aka canza container. **Volumes** suna warware wannan ta hanyar ba da **Docker-managed persistent storage** da ke zaune a waje da container's lifecycle, saboda haka data (databases, uploads, kowane state) na tsugunar container removal da replacement — dole ne don stateful applications.

Sanin **bind mounts** (mapping a host directory zuwa container) abu ne mai mahimmanci don **development** (gyara code a kan host da ganin changes live a cikin container, aiki na development da aka fi yi) da don sharing host files.

Sanin **distinction** — volumes (Docker-managed, portable, zabin da aka fi so don persistent application data kamar databases) versus bind mounts (host-path-specific, kyau don development) — yana jawo kan zabin hanya ta dace.

Tun da containers su ephemeral ne ta design kuma most real applications suna da data da sai ya tsugunar (databases musamman), kuma tun da volumes su mekanisim da ke mahimmanci don persistent storage (tare da bind mounts da ke mahimmanci don development), sanin Docker data persistence — ephemeral-container matsalar, volumes don persistent data, bind mounts don development, da lokacin amfani da kowane — abu ne da ya zama dole, practically-relevant Docker knowledge, dole ne don running stateful applications daidai kuma tsogon kuskuren ba data da aka store a ciki disposable containers.