{"id":614,"date":"2026-10-02T12:00:00","date_gmt":"2026-10-02T12:00:00","guid":{"rendered":"https:\/\/konteynerium.com\/index.php\/2026\/10\/02\/multi-stage-build-ile-kucuk-imajlar\/"},"modified":"2026-10-02T12:00:00","modified_gmt":"2026-10-02T12:00:00","slug":"multi-stage-build-ile-kucuk-imajlar","status":"publish","type":"post","link":"https:\/\/konteynerium.com\/index.php\/2026\/10\/02\/multi-stage-build-ile-kucuk-imajlar\/","title":{"rendered":"Multi-Stage Build ile K\u00fc\u00e7\u00fck ve G\u00fcvenli \u0130majlar"},"content":{"rendered":"

Bir uygulamay\u0131 derlemek i\u00e7in gereken ara\u00e7lar (derleyici, geli\u015ftirme k\u00fct\u00fcphaneleri, test ara\u00e7lar\u0131) \u00e7al\u0131\u015ft\u0131rmak i\u00e7in gerekenlerden \u00e7ok daha fazlad\u0131r. Tek bir Dockerfile ile build eden bir imaj bu ara\u00e7lar\u0131n hepsini \u00fcretime ta\u015f\u0131r: gereksiz yere b\u00fcy\u00fck, daha yava\u015f indirilen ve sald\u0131r\u0131 y\u00fczeyi geni\u015f bir imaj. Multi-stage build<\/strong> bu sorunu tek bir Dockerfile i\u00e7inde, birden fazla FROM<\/code> kullanarak \u00e7\u00f6zer.<\/p>\n

Fikir: derle bir yerde, \u00e7al\u0131\u015ft\u0131r ba\u015fka yerde<\/h2>\n

Her FROM<\/code> yeni bir “a\u015fama” (stage) ba\u015flat\u0131r. Bir a\u015famada derlersiniz; son a\u015famada ise yaln\u0131zca derleme \u00e7\u0131kt\u0131s\u0131n\u0131 COPY --from<\/code> ile al\u0131p temiz bir imaja koyars\u0131n\u0131z. \u00d6nceki a\u015famalar nihai imaja girmez.<\/p>\n

# A\u015fama 1 \u2014 derleme (b\u00fcy\u00fck ara\u00e7 seti burada)\nFROM temel-imaj AS build\nRUN head -c 30000000 \/dev\/zero > \/buyuk-arac-seti.bin\nRUN echo \"derlenmis-uygulama\" > \/app.bin\n\n# A\u015fama 2 \u2014 nihai imaj (yaln\u0131zca \u00e7\u0131kt\u0131)\nFROM temel-imaj\nCOPY --from=build \/app.bin \/app.bin\nCMD [\"\/bin\/cat\", \"\/app.bin\"]<\/code><\/pre>\n
Burada 30 MB’l\u0131k “ara\u00e7 seti” yaln\u0131zca build<\/code> a\u015famas\u0131nda vard\u0131r. Ayn\u0131 i\u015fi tek a\u015famada yapan s\u00fcr\u00fcmle kar\u015f\u0131la\u015ft\u0131ral\u0131m:<\/p>\n
$ docker images --format '{{.Repository}}:{{.Tag}} {{.Size}}' | sort\nms:multi   21.1MB\nms:single  51.2MB<\/code><\/pre>\n
Tek a\u015famal\u0131 imaj 51,2 MB<\/strong>, multi-stage imaj 21,1 MB<\/strong> \u2014 fark, ara\u00e7 setinin nihai imaja girmemesinden gelir. Ger\u00e7ek projelerde bu fark \u00e7ok daha dramatiktir (derleyici ve ba\u011f\u0131ml\u0131l\u0131klar y\u00fczlerce MB olabilir).<\/p>\n
A\u015famalara ad verin<\/h2>\n
AS ad<\/code> ile a\u015famalara isim verebilirsiniz; COPY --from=build<\/code> gibi referanslar s\u0131raya (--from=0<\/code>) ba\u011f\u0131ml\u0131 olmaz ve Dockerfile’a yeni a\u015fama ekledi\u011finizde bozulmaz. Ba\u015fka bir imajdan da do\u011frudan dosya kopyalayabilirsiniz:<\/p>\n
COPY --from=nginx:latest \/etc\/nginx\/nginx.conf \/nginx.conf<\/code><\/pre>\n
Belirli bir a\u015famada durmak: --target<\/code><\/h2>\n
Hata ay\u0131klarken ya da sadece test a\u015famas\u0131n\u0131 \u00e7al\u0131\u015ft\u0131rmak istedi\u011finizde --target<\/code> ile build’i o a\u015famada durdurabilirsiniz:<\/p>\n
docker build --target build -t ornek:build .<\/code><\/pre>\n
Dikkat: --target build<\/code> ile \u00fcretilen imaj, nihai imaj de\u011fil build a\u015famas\u0131n\u0131n tamam\u0131d\u0131r<\/em>; bizim denememizde 51,2 MB \u00e7\u0131kt\u0131. Bu imaj\u0131 \u00fcretime g\u00f6ndermemeniz gerekti\u011fini unutmay\u0131n.<\/p>\n
BuildKit gereksiz a\u015famalar\u0131 atlar<\/h2>\n
Dockerfile’a \u015f\u00f6yle bir test<\/code> a\u015famas\u0131 ekleyelim, ama nihai a\u015fama bundan hi\u00e7bir \u015fey kopyalamas\u0131n:<\/p>\n
FROM temel-imaj AS test\nCOPY --from=build \/app.bin \/app.bin\nRUN echo \"testler gecti\"<\/code><\/pre>\n
BuildKit (Docker’\u0131n modern build motoru ve varsay\u0131lan builder) yaln\u0131zca hedef a\u015faman\u0131n ba\u011f\u0131ml\u0131 oldu\u011fu a\u015famalar\u0131 \u00e7al\u0131\u015ft\u0131r\u0131r. --progress=plain<\/code> \u00e7\u0131kt\u0131s\u0131n\u0131 inceledi\u011fimizde test<\/code> a\u015famas\u0131n\u0131n hi\u00e7 \u00e7al\u0131\u015fmad\u0131\u011f\u0131n\u0131 do\u011frulad\u0131k. Bu \u00f6zelli\u011fi “iste\u011fe ba\u011fl\u0131” a\u015famalar i\u00e7in kullanabilirsiniz: test a\u015famas\u0131n\u0131 yaln\u0131zca CI’da --target test<\/code> ile \u00e7al\u0131\u015ft\u0131r\u0131n, normal build’de hi\u00e7 \u00e7al\u0131\u015fmas\u0131n.<\/p>\n
Ger\u00e7ek d\u00fcnya kal\u0131b\u0131<\/h2>\n
Yayg\u0131n bir kal\u0131p, derleme i\u00e7in tam bir SDK imaj\u0131, \u00e7al\u0131\u015ft\u0131rma i\u00e7in minimal bir imaj kullanmakt\u0131r. \u00d6rne\u011fin bir Go uygulamas\u0131nda:<\/p>\n
FROM golang:1.26 AS build\nWORKDIR \/src\nCOPY . .\nRUN CGO_ENABLED=0 go build -o \/bin\/uygulama .\n\nFROM scratch\nCOPY --from=build \/bin\/uygulama \/bin\/uygulama\nENTRYPOINT [\"\/bin\/uygulama\"]<\/code><\/pre>\n
Statik derlenmi\u015f bir ikili scratch<\/code> (bo\u015f) imajda \u00e7al\u0131\u015fabilir; sonu\u00e7 birka\u00e7 MB’l\u0131k, i\u00e7inde kabuk bile bulunmayan bir imajd\u0131r. Node.js, Python ya da Java gibi \u00e7al\u0131\u015fma zaman\u0131 gerektiren dillerde son a\u015fama genellikle -slim<\/code>, alpine<\/code> ya da distroless bir imaj olur (bkz. Container Image G\u00fcvenli\u011fi<\/a>).<\/p>\n
\n  \u2713<\/span><\/p>\n
G\u00fcvenlik kazanc\u0131 da vard\u0131r: derleyici, paket y\u00f6neticisi ve test ara\u00e7lar\u0131 nihai imajda olmad\u0131\u011f\u0131 i\u00e7in, bir sald\u0131rgan container’a s\u0131zsa bile elinde kullanabilece\u011fi ara\u00e7 \u00e7ok azd\u0131r.<\/p>\n<\/div>\n
H\u0131zl\u0131 kontrol listesi<\/h2>\n