Menene bambanci tsakanin ENTRYPOINT da CMD?

Question

Accepted Answer

**ENTRYPOINT** da **CMD** duk suna bayyana abin da zai gudu yayin da container ya fara, amma suna aiki da bukatarun daban-daban kuma suna haɗa ta wata hanya ta musamman. Fahimtar bambanci (da nau'i biyu — exec da shell) yana da muhimmanci don rubuta Dockerfiles da ke aiki daidai.

## CMD — umarni na tsohuwa (ana iya canza shi)

```dockerfile
CMD ["node", "server.js"]
# → the DEFAULT command when the container starts
# → but it's REPLACED if you pass a command at run time:
#   docker run myapp echo hello   → runs "echo hello" INSTEAD of node server.js
```

`CMD` yana ba da **umarni na tsohuwa**, wanda **dule dule aka canza** ta kowane umarni da aka ba a `docker run`.

## ENTRYPOINT — aiwatacciyar dokoki na tsohuwa

```dockerfile
ENTRYPOINT ["node", "server.js"]
# → ALWAYS runs; run-time arguments are APPENDED (not replacing it):
#   docker run myapp --port 8080   → runs "node server.js --port 8080"
# → makes the container behave like a specific executable
```

`ENTRYPOINT` yana saita **aiwatacciyar dokoki na tsohuwa** da koda yaushe suke aiki; hujjaji na lokacin gudu ana **haɗa su** azaman hujjajin niyansa maimakon canza shi.

## Aiwatar da su tare (niga na gida)

```dockerfile
ENTRYPOINT ["node", "server.js"]   # the fixed command
CMD ["--port", "3000"]              # DEFAULT arguments (overridable)
# docker run myapp                  → node server.js --port 3000 (defaults)
# docker run myapp --port 8080      → node server.js --port 8080 (CMD overridden)
→ ENTRYPOINT = the command; CMD = default arguments you can override. A clean pattern.
```

## Nau'i na Exec da nau'i na shell

```text
EXEC form  → CMD ["node", "server.js"]  (JSON array) — PREFERRED:
  runs the executable DIRECTLY (PID 1) → receives signals (SIGTERM) → graceful shutdown
SHELL form → CMD node server.js  → runs via /bin/sh -c → the shell is PID 1,
  the app may NOT receive signals properly (shutdown issues) → avoid for the main process
```

## Me yake da mahimmanci

Fahimtar bambanci tsakanin ENTRYPOINT da CMD yana da mahimmanci don **rubuta Dockerfiles da ke aiki daidai**, don haka yana da mahimmanci ilimin aiki-aiki kuma jiya ruwan jiya a takaice.

Bambancin iko yana da tasiri: **CMD** yana ba da umarni na tsohuwa da **dule dule aka canza** ta kowane umarni da aka pass zuwa `docker run`, yayin da **ENTRYPOINT** yana saita aiwatacciyar dokoki na tsohuwa da koda yaushe suke aiki tare da hujjaji na lokacin gudu **aka haɗa** zuwa gida — daban-dabanniyar iko da ke tasira a yadda container ke amsa hujjaji na lokacin gudu.

Fahimtar **niga na gida na aiwatar da su tare** (`ENTRYPOINT` azaman umarni da `CMD` azaman hujjaji na tsohuwa na iya canzawa) niga mai tsauri, idiomatic ne wanda ke sa containers su yi amfani kamar aiwatacciyar dokoki na yana iya daidaita — iyake da aka yi amal dashi sannu da yawa da shine bakin jiya a saniya.

Tun gida, fahimtar **nau'i na exec da nau'i na shell** yana da mahimmanci don daidaituwa: **nau'i na exec** (jerin JSON, m. `CMD ["node", "server.js"]`) shine an fi so shi ne saboda yana aiwatar aiwatacciyar dokoki **jiya zuwa PID 1**, don haka **yana karbi alamomi kamar SIGTERM** daidai, abubuwan da ke baiwa **jiya ta aminci** — yayin da **nau'i na shell** (`CMD node server.js`) yana aiwatar ta shell da ke zama PID 1, sau da yawa aikina **ba sa karbi alamomi na jiya daidai** (gida mai saurin gudu, saurin jiya, ko jiya mai saurin jiya).

Bu bambanci ne na tikela/mai kyau-kyau jiya wanda nau'i na exec ke kare shi.

Wanan saita abin da zai gudu yayin da container ya fara yana da mahimmanci ga kowane Dockerfile, kuma tun wannan ENTRYPOINT/CMD bambanci (da exec-vs-shell-form tikela-dandano mahimmanci) da ke tasira jija akan amfani da container da daidaituwa (hujja jiya, mai kyau-kyau jiya), fahimtar ENTRYPOINT da CMD — niyoyin su, yadda suke haɗa, da mahimmacin exec-form-for-signals aiki — yana da mahimmanci, aiki-aiki bakin jiya ilimi, jiya ruwan jiya a takaice-takaice matakin inda fahimtar bambanci ke kiyaye amfani da container da daidaituwa da jiya bambanci.