Kuna tofauti gani kati ya Docker images na containers?

Question

Accepted Answer

Docker **image** ni **kiolezo** cha kusoma-tu (programu iliyofungashwa na tegemezi zake); **container** ni **kiendeshaji kinachoendesha** cha image. Uhusiano ni kama class na object: image moja inaweza kuzaa containers nyingi. ## Image dhidi ya 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) ``` ## Kufanya kazi na 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 hujengwa (kutoka Dockerfile), huhifadhiwa kienyeji au katika registries, hupewa matoleo kwa tags (`myapp:1.0`), na hushirikiwa. ## Kufanya kazi na 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 huundwa kutoka images, zina mzunguko wa maisha (run, stop, start, remove), na unaweza kukagua logs au kuingia (exec) ndani yao. ## Uhusiano wa tabaka (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 ``` ## Kwa nini ni muhimu Kuelewa tofauti kati ya images na containers ni msingi wa kufanya kazi na Docker, hivyo ni maarifa muhimu ya lazima-kujua. Uhusiano — **image** ni **kiolezo** cha kusoma-tu (programu iliyofungashwa na tegemezi, kama blueprint au class) wakati **container** ni **kiendeshaji kinachoendesha** cha image hiyo (kama object iliyoundwa kutoka class, yenye hali ya runtime) — ni modeli kuu ya kidhana ya Docker, na kuvichanganya viwili husababisha mkanganyiko kuhusu jinsi Docker inavyofanya kazi. Kuelewa kwamba **image moja inaweza kuzaa containers nyingi** (kuendesha image hiyo hiyo mara nyingi) ni muhimu kwa jinsi Docker inavyowezesha scaling na ulinganifu. Kujua shughuli za kivitendo — kujenga, kuorodhesha, kuvuta (pull), kusukuma (push), na kupeana matoleo **images** (kwa tags kama `myapp:1.0`), na kuendesha, kusimamisha, kukagua (logs), na kuingia (exec) ndani ya **containers** (kusimamia mzunguko wao wa maisha) — ni maarifa ya kivitendo ya kila siku ya kutumia Docker. Kuelewa **uhusiano wa tabaka** (images zinazojengwa kwa tabaka zilizo-cached na zinazoshirikiwa; container ikiwa tabaka za kusoma-tu za image pamoja na tabaka nyembamba inayoweza kuandikwa ambapo mabadiliko ya runtime huenda, yanayopotea wakati wa kuondolewa isipokuwa yamehifadhiwa kupitia volumes) kunaeleza ufanisi wa Docker (kushiriki/ku-cache tabaka) na tahadhari muhimu (mabadiliko ya container ni ya muda bila volumes). Kwa kuwa tofauti ya image/container ni modeli ya msingi ya kiakili kwa Docker, na kwa kuwa kuielewa (na shughuli zinazohusiana na muundo wa tabaka) ni lazima kwa kujenga, kuendesha, na kusimamia mizigo ya kazi ya Docker kwa usahihi, kuelewa tofauti kati ya images na containers ni maarifa muhimu ya msingi ya Docker — dhana kuu ambayo kila kitu kingine katika Docker hujengwa juu yake, na tofauti ambayo kila mtumiaji wa Docker lazima aielewe wazi.