Apa bedane antarane Docker images lan containers?

Question

Accepted Answer

A Docker **image** punika **template** sing maca-mung (aplikasi sing di-package sareng dependencies-ne); a **container** punika **running instance** saka image. Hubungan-ne kaya kelas lan obyek: siji image bisa nyebulake akeh containers. ## Image versus container ```text IMAGE → a read-only TEMPLATE: the app + dependencies + config, built in layers (like a blueprint/class; stored, shared, versioned) CONTAINER → a RUNNING INSTANCE of an image (with a writable layer on top) (like an object created from a class; has runtime state) One IMAGE → many CONTAINERS (run the same image multiple times) ``` ## Nggarap sareng images ```bash docker build -t myapp:1.0 . # BUILD an image from a Dockerfile docker images # list local images docker pull nginx # download an image from a registry docker push myapp:1.0 # upload an image to a registry docker rmi myapp:1.0 # remove an image ``` Images dibangun (saka Dockerfile), disimpan lokal utawa ing registries, diversi sareng tags (`myapp:1.0`), lan dibagi. ## Nggarap sareng containers ```bash docker run -d -p 80:80 nginx # RUN a container from an image (-d = background) docker ps # list RUNNING containers docker ps -a # list all (including stopped) docker stop # stop a container docker start # start a stopped container docker rm # remove a container docker logs # view a container's logs docker exec -it bash # run a command inside a running container ``` Containers digawa saka images, nduweni lifecycle (run, stop, start, remove), lan sampeyan bisa inspeksi logs utawa exec menyang içe. ## Hubungan layered ```text → Images are built in LAYERS (each Dockerfile instruction adds a layer, cached/shared) → A container = the image's read-only layers + a thin WRITABLE layer on top → Changes in a running container go to its writable layer (lost when removed, unless persisted via volumes) — the underlying image is unchanged ``` ## Apa kok penting Mangerti bedane antarane images lan containers punika fundamental kanggo nggarap sareng Docker, dadi iku kudu diduweni. Hubungan - siji **image** punika **template** sing maca-mung (aplikasi sing di-package sareng dependencies, kaya blueprint utawa kelas) dene siji **container** punika **running instance** saka image kuwi (kaya obyek sing digawa saka kelas, sareng runtime state) - kuwi punika core conceptual model saka Docker, lan kaliren kalih-kalihé nyebabake kaliren babagan kepriyé Docker katon. Mangerti yen **siji image bisa nyebulake akeh containers** (menjalanke image sing padha berkali-kali) punika kunci kepriyé Docker ngaktifake scaling lan consistency. Kasuwan operasi praktis - building, listing, pulling, pushing, lan versioning **images** (sareng tags kaya `myapp:1.0`), lan running, stopping, inspecting (logs), lan exec-ing menyang **containers** (manage lifecycle-ne) - punika kasuwan praktis kanggo nggunakake Docker. Mangerti **hubungan layered** (images dibangun ing cached, shareable layers; siji container punika image's read-only layers plus thin writable layer endi runtime changes tindak, ilang ing removal kajaba persisted via volumes) njelaske loro-lorone Docker's efficiency (layer sharing/caching) lan siji important gotcha (container changes punika ephemeral tanpa volumes). Amarga image/container distinction punika foundational mental model kanggo Docker, lan amarga mangerti iku (lan associated operations lan layered structure) kudu kanggo building, running, lan managing Docker workloads kanthi bener, mangerti bedane antarane images lan containers punika essential, fundamental Docker knowledge - core concept sing liyane-liyané Docker build ing dhuwur, lan siji distinction sing kudu ngerti kanthi jelas dening saben Docker user.