Apa iku build context lan kenapa nggunakake file .dockerignore?

Question

Accepted Answer

Nalika sampeyan njalanake `docker build`, Docker ngirim **build context** (file-file ing direktori build) menyang daemon. File **.dockerignore** nyingkiri file-file sing ora perlu saka konteks kasebut — nyepatin build, nyilikake ukuran image, lan nyegah kebocoran file sensitif.

## Build context

```bash
docker build -t myapp .     # the "." is the build context — the directory sent to the daemon
# → Docker tarballs the ENTIRE context directory and sends it to the daemon BEFORE building
# → a big context (node_modules, .git, large files) = slow builds, more data transferred
```

**Build context** minangka set file sing Docker kirim menyang daemon kanggo mbangun image. Kabeh sing ana ing direktori build kalebokake kajaba sing diksingkiri — dadi konteks sing gemuk bengi saben build.

## .dockerignore — nyingkiri file sing ora dibutuhake

```text
# .dockerignore (like .gitignore, for the build context)
node_modules        # don't send local deps (they're installed in the image anyway)
.git                # don't send version history
*.log
.env                # ⚠️ don't send SECRETS into the build context/image
Dockerfile
dist
.vscode
```

`.dockerignore` bisa dienggo kaya `.gitignore`, nyingkiri file saka build context.

## Kenapa iku penting (telung benefit)

```text
✓ FASTER builds — a smaller context transfers faster; fewer files to process
  (also helps caching: COPY . . won't be invalidated by irrelevant file changes)
✓ SMALLER images — excluded files (node_modules, .git) don't get COPYed into the image
✓ SECURITY — keep SECRETS (.env, keys, credentials) out of the context AND the image
  (a COPY . . could otherwise copy a .env file into the image — a real leak risk)
```

## Kenapa iku penting

Paham babagan build context lan `.dockerignore` penting kanggo **efficient lan secure Docker builds**, dadi kasunyatan ngewayani pengetahuan sing berguna.

Lawas-lawas developer ora ngerti menawa `docker build .` ngirim **kabeh direktori build-context menyang daemon** sadurunge mbangun — dadi konteks sing gemuk (ngemot `node_modules`, `.git`, build artifacts, file gedhe) nggawe **saben build luwih alon** (akeh data sing kudu dipindahake lan diproses) lan risiko nyalin file sing ora kepingin menyang image.

File **.dockerignore** (bisa dienggo kaya `.gitignore`) ngatasi iku kanthi telung benefit konkret: **build luwih cepet** (konteks sing cilik liwat lan diproses luwih cepet, lan uga nambahi layer caching amarga `COPY . .` ora bakal dibatalke dening owah-owahan file sing ora relevan), **image luwih cilik** (file sing diksingkiri ora dikopiak — contone ora nggabung `node_modules` lokal sing dipasang maneh), lan penting banget **security** (njaga **secrets kaya file `.env`, key, lan credentials saka build context lan image** — amarga `COPY . .` bakal nyalin `.env` menyang image, risiko nyata lan umum bocor kredensyal).

Benefit security iku khususy penting, amarga kabetulane masang secrets utawa file sensitif menyang image liwat copy sing luwih jembar minangka kesalahan nyata sing `.dockerignore` bantu nyegah.

Amarga build temenan lan build efficiency, ukuran image, lan nyegah kebocoran secret kabeh penting, lan amarga paham babagan build context lan nggunakake `.dockerignore` langsung nambahi kabeh telu, paham babagan build context lan `.dockerignore` minangka pengetahuan Docker sing berharga, praktis-relevan — praktik sederhana nanging penting kanggo build cepet, ramping, lan aman sing gampang ditinggali nanging maana banget ngungsine, khususy kanggo nyegah kalebokane secrets aksidental menyang image.