{"id":612,"date":"2026-09-30T12:00:00","date_gmt":"2026-09-30T12:00:00","guid":{"rendered":"https:\/\/konteynerium.com\/index.php\/2026\/09\/30\/dockerignore-ve-build-baglami-docker-build-neden-yavas\/"},"modified":"2026-09-30T12:00:00","modified_gmt":"2026-09-30T12:00:00","slug":"dockerignore-ve-build-baglami-docker-build-neden-yavas","status":"publish","type":"post","link":"https:\/\/konteynerium.com\/index.php\/2026\/09\/30\/dockerignore-ve-build-baglami-docker-build-neden-yavas\/","title":{"rendered":".dockerignore ve Build Ba\u011flam\u0131: docker build Neden Yava\u015f ve \u015ei\u015fkin?"},"content":{"rendered":"

docker build .<\/code> komutundaki o k\u00fc\u00e7\u00fck nokta asl\u0131nda \u00f6nemli bir \u015fey s\u00f6yler: “build ba\u011flam\u0131<\/strong> (build context) bu dizindir.” Docker, build ba\u015flarken bu dizinin i\u00e7eri\u011fini build motoruna g\u00f6nderir. Dizinde b\u00fcy\u00fck dosyalar, node_modules<\/code> ya da gizli bir .env<\/code> varsa; build yava\u015flar, imaj \u015fi\u015fer ve \u2014 en k\u00f6t\u00fcs\u00fc \u2014 o gizli dosya imaj\u0131n i\u00e7ine girebilir.<\/p>\n

Ba\u011flam ger\u00e7ekte ne kadar b\u00fcy\u00fck?<\/h2>\n

\u00d6rnek bir proje d\u00fc\u015f\u00fcnelim: 50 MB’l\u0131k bir veri dosyas\u0131, 20 MB’l\u0131k bir node_modules<\/code> klas\u00f6r\u00fc, bir .env<\/code> dosyas\u0131 ve k\u00fc\u00e7\u00fck bir app.txt<\/code>. Dockerfile ise yaln\u0131zca t\u00fcm klas\u00f6r\u00fc kopyal\u0131yor:<\/p>\n

FROM temel-imaj\nCOPY . \/app<\/code><\/pre>\n
BuildKit’in ayr\u0131nt\u0131l\u0131 \u00e7\u0131kt\u0131s\u0131nda (--progress=plain<\/code>) ba\u011flam\u0131n boyutu g\u00f6r\u00fcn\u00fcr:<\/p>\n
$ docker build --progress=plain -t ornek:1 .\n...\n#5 transferring context: 70.02MB 0.9s done<\/code><\/pre>\n
Tek sat\u0131rl\u0131k uygulama i\u00e7in 70 MB<\/strong> g\u00f6nderildi \u2014 ve COPY . \/app<\/code> bunlar\u0131n hepsini (gizli .env<\/code> dahil) imaja yazd\u0131. Her docker build<\/code>‘da bu transfer tekrar edilir.<\/p>\n
.dockerignore ile \u00e7\u00f6z\u00fcm<\/h2>\n
Ba\u011flam dizininin k\u00f6k\u00fcne .dockerignore<\/code> dosyas\u0131 koyun. Bi\u00e7imi .gitignore<\/code>‘a benzer; listelenen yollar build ba\u011flam\u0131na hi\u00e7 g\u00f6nderilmez<\/em>:<\/p>\n
node_modules\n*.bin\n.env\n.git<\/code><\/pre>\n
Ayn\u0131 build’i yeniden \u00e7al\u0131\u015ft\u0131rd\u0131\u011f\u0131m\u0131zda:<\/p>\n
#5 transferring context: 124B 0.0s done\n\n$ docker run --rm ornek:2 ls -A \/app\n.dockerignore\nDockerfile\napp.txt<\/code><\/pre>\n
70 MB’dan 124 bayta<\/strong> d\u00fc\u015ft\u00fc; .env<\/code>, node_modules<\/code> ve b\u00fcy\u00fck dosya imajda yok. Bu dosya ayn\u0131 zamanda \u00f6nbelle\u011fi de korur: ilgisiz bir dosya (\u00f6rne\u011fin bir log) de\u011fi\u015fti\u011finde COPY . .<\/code> katman\u0131 gereksiz yere ge\u00e7ersiz kalmaz.<\/p>\n
\n  !<\/span><\/p>\n
.dockerignore<\/code> bir g\u00fcvenlik \u00f6nlemi olarak da d\u00fc\u015f\u00fcn\u00fclmelidir: .env<\/code>, *.pem<\/code>, .git<\/code> gibi dosyalar\u0131 buraya yazmak, COPY . .<\/code> ile yanl\u0131\u015fl\u0131kla imaja girmelerini engeller. Detay i\u00e7in Container Image G\u00fcvenli\u011fi<\/a> yaz\u0131s\u0131na bak\u0131n.<\/p>\n<\/div>\n
S\u0131k kullan\u0131lan kal\u0131plar<\/h2>\n\n\n\n\n\n\n\n\n\n\n
Sat\u0131r<\/th>\nNe yapar?<\/th>\n<\/tr>\n<\/thead>\n
node_modules<\/code><\/td>\nBa\u011f\u0131ml\u0131l\u0131klar\u0131 imaj i\u00e7inde npm ci<\/code> ile kurdu\u011funuz i\u00e7in host’taki kopyay\u0131 d\u0131\u015far\u0131da b\u0131rak\u0131r<\/td>\n<\/tr>\n
.git<\/code><\/td>\nDepo ge\u00e7mi\u015fini (genellikle b\u00fcy\u00fck) ba\u011flamdan \u00e7\u0131kar\u0131r<\/td>\n<\/tr>\n
*.log<\/code>, tmp*<\/code><\/td>\nGe\u00e7ici ve log dosyalar\u0131<\/td>\n<\/tr>\n
.env*<\/code><\/td>\nOrtam ve gizli bilgi dosyalar\u0131<\/td>\n<\/tr>\n
Dockerfile<\/code>, .dockerignore<\/code><\/td>\n\u0130maja girmesi gerekmeyen yap\u0131land\u0131rma (bu dosyalar yine de build’e okunur)<\/td>\n<\/tr>\n
!istisna.txt<\/code><\/td>\n!<\/code> ile bir \u00f6nceki kural\u0131n istisnas\u0131 tan\u0131mlan\u0131r<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Not: Yukar\u0131daki deneyde Dockerfile<\/code> ve .dockerignore<\/code>‘\u0131 listeye yazmad\u0131\u011f\u0131m\u0131z i\u00e7in COPY . \/app<\/code> bunlar\u0131 da imaja kopyalad\u0131 (ls<\/code> \u00e7\u0131kt\u0131s\u0131ndaki iki dosya). Listeye yazarsan\u0131z imaja girmezler; build motoru yine de onlar\u0131 build talimatlar\u0131 i\u00e7in okur.<\/p>\n
B\u00fcy\u00fck ba\u011flam\u0131 fark etmenin yollar\u0131<\/h2>\n