C#•2mo ago

Docker build time is too big

i have 3 services in docker compose that depends_on each other, here is my docker compose file:

networks:
  dev:
    driver: bridge

services:
  animuvn-info:
    depends_on:
      - "api-animuvn-info"
    build:
      context: .
      dockerfile: AnimeVnInfoFrontend/Dockerfile
    networks:
      - dev

  api-animuvn-info:
    depends_on:
      - "postgres"
      - "api-animuvn-info-admin"
    build:
      context: .
      dockerfile: AnimeVnInfoBackend/AnimeVnInfoBackend/Dockerfile
    networks:
      - dev

  api-animuvn-info-admin:
    depends_on:
      - "postgres"
    build:
      context: .
      dockerfile: AnimeVnInfoBackend/AnimeVnInfoBackend.Admin/Dockerfile
    networks:
      - dev

  postgres:
    image: postgres:latest

  nginx:
    image: nginx:latest

volumes:

networks:
  dev:
    driver: bridge

services:
  animuvn-info:
    depends_on:
      - "api-animuvn-info"
    build:
      context: .
      dockerfile: AnimeVnInfoFrontend/Dockerfile
    networks:
      - dev

  api-animuvn-info:
    depends_on:
      - "postgres"
      - "api-animuvn-info-admin"
    build:
      context: .
      dockerfile: AnimeVnInfoBackend/AnimeVnInfoBackend/Dockerfile
    networks:
      - dev

  api-animuvn-info-admin:
    depends_on:
      - "postgres"
    build:
      context: .
      dockerfile: AnimeVnInfoBackend/AnimeVnInfoBackend.Admin/Dockerfile
    networks:
      - dev

  postgres:
    image: postgres:latest

  nginx:
    image: nginx:latest

volumes:

but when i hit the command docker compose build, all of these 3 services don't build sequentially after i updated docker to 4.43.1, the build time is very big, does anyone know why that happens?

99 Replies

Keswiik•2mo ago

have you tried building these services in order of their dependencies to diagnose which one might be causing slowdowns?

A Ka SupOP•2mo ago

no...

Keswiik•2mo ago

well, that's an easy place to start

A Ka SupOP•2mo ago

but before i updated my docker desktop, the 3 services is built from admin, after it finished the build, then api-animuvn-info started, then animuvn-info started at the last

Keswiik•2mo ago

and? it's probably still building the same way but with different console output

Unknown User•2mo ago

Message Not Public

A Ka SupOP•2mo ago

i don't understand, i just hit docker compose build, before updated it happened like i said above, now all of these services run the build simultaneously

Unknown User•2mo ago

Message Not Public

A Ka SupOP•2mo ago

no.... i did the docker compose build hundred times, there's no postgre or nginx pull

Unknown User•2mo ago

Message Not Public

A Ka SupOP•2mo ago

the point i want to say is 3 services run the build simultaneously at version 4.43.1, before this version (im not sure) they run sequentially, i hit that command so many times

Unknown User•2mo ago

Message Not Public

Keswiik•2mo ago

i'm not sure what point you're trying to make so maybe try what teb or i have suggested to diagnose what changed (or broke) instead of continuing to reference past behavior....?

Unknown User•2mo ago

Message Not Public

A Ka SupOP•2mo ago

:sadge:

Unknown User•2mo ago

Message Not Public

A Ka SupOP•2mo ago

:sadge:

Keswiik•2mo ago

^ with just a compose file and one screenshot of a running build with 0 logs, there's nothing we can suggest besides 'try getting logs and/or building differently'

Unknown User•2mo ago

Message Not Public

A Ka SupOP•2mo ago

the dockerfile is just some commands to build, restore, publish, why its important

Unknown User•2mo ago

Message Not Public

Keswiik•2mo ago

bro your dockerfile is what's being used when you run docker compose build so uh, yeah, it does the heavy lifting in this situation

Unknown User•2mo ago

Message Not Public

Keswiik•2mo ago

can probably get logs without a full prune as well, just try building the services individually and see what happens (with that progress flag)

Unknown User•2mo ago

Message Not Public

A Ka SupOP•2mo ago

one of my dockerfile

FROM mcr.microsoft.com/dotnet/aspnet:9.0 AS base
USER app
WORKDIR /app
EXPOSE 8080

ENV ASPNETCORE_URLS=http://+:8080

FROM mcr.microsoft.com/dotnet/sdk:9.0 AS build
ARG BUILD_CONFIGURATION=Release
WORKDIR /src
COPY ["AnimeVnInfoBackend/AnimeVnInfoBackend/AnimeVnInfoBackend.csproj", "AnimeVnInfoBackend/AnimeVnInfoBackend/"]
COPY ["AnimeVnInfoBackend/AnimeVnInfoBackend.AuthorizePolicy/AnimeVnInfoBackend.AuthorizePolicy.csproj", "AnimeVnInfoBackend/AnimeVnInfoBackend.AuthorizePolicy/"]
COPY ["AnimeVnInfoBackend/AnimeVnInfoBackend.Configure/AnimeVnInfoBackend.Configure.csproj", "AnimeVnInfoBackend/AnimeVnInfoBackend.Configure/"]
COPY ["AnimeVnInfoBackend/AnimeVnInfoBackend.Hub/AnimeVnInfoBackend.Hub.csproj", "AnimeVnInfoBackend/AnimeVnInfoBackend.Hub/"]
COPY ["AnimeVnInfoBackend/AnimeVnInfoBackend.Model/AnimeVnInfoBackend.Model.csproj", "AnimeVnInfoBackend/AnimeVnInfoBackend.Model/"]
COPY ["AnimeVnInfoBackend/AnimeVnInfoBackend.Repository/AnimeVnInfoBackend.Repository.csproj", "AnimeVnInfoBackend/AnimeVnInfoBackend.Repository/"]
COPY ["AnimeVnInfoBackend/AnimeVnInfoBackend.Service/AnimeVnInfoBackend.Service.csproj", "AnimeVnInfoBackend/AnimeVnInfoBackend.Service/"]
COPY ["AnimeVnInfoBackend/AnimeVnInfoBackend.Utility/AnimeVnInfoBackend.Utility.csproj", "AnimeVnInfoBackend/AnimeVnInfoBackend.Utility/"]
COPY ["AnimeVnInfoBackend/AnimeVnInfoBackend.View/AnimeVnInfoBackend.View.csproj", "AnimeVnInfoBackend/AnimeVnInfoBackend.View/"]
RUN dotnet restore "./AnimeVnInfoBackend/AnimeVnInfoBackend/AnimeVnInfoBackend.csproj"
COPY . .
WORKDIR "/src/AnimeVnInfoBackend/AnimeVnInfoBackend"

FROM build AS publish
ARG BUILD_CONFIGURATION=Release
RUN dotnet publish "./AnimeVnInfoBackend.csproj" -c $BUILD_CONFIGURATION -o /app/publish /p:UseAppHost=false

FROM base AS final
WORKDIR /app
COPY --from=publish --chown=app:app /app/publish .
RUN mkdir /app/Image
RUN mkdir /app/Logs
ENTRYPOINT ["dotnet", "AnimeVnInfoBackend.dll"]

FROM mcr.microsoft.com/dotnet/aspnet:9.0 AS base
USER app
WORKDIR /app
EXPOSE 8080

ENV ASPNETCORE_URLS=http://+:8080

FROM mcr.microsoft.com/dotnet/sdk:9.0 AS build
ARG BUILD_CONFIGURATION=Release
WORKDIR /src
COPY ["AnimeVnInfoBackend/AnimeVnInfoBackend/AnimeVnInfoBackend.csproj", "AnimeVnInfoBackend/AnimeVnInfoBackend/"]
COPY ["AnimeVnInfoBackend/AnimeVnInfoBackend.AuthorizePolicy/AnimeVnInfoBackend.AuthorizePolicy.csproj", "AnimeVnInfoBackend/AnimeVnInfoBackend.AuthorizePolicy/"]
COPY ["AnimeVnInfoBackend/AnimeVnInfoBackend.Configure/AnimeVnInfoBackend.Configure.csproj", "AnimeVnInfoBackend/AnimeVnInfoBackend.Configure/"]
COPY ["AnimeVnInfoBackend/AnimeVnInfoBackend.Hub/AnimeVnInfoBackend.Hub.csproj", "AnimeVnInfoBackend/AnimeVnInfoBackend.Hub/"]
COPY ["AnimeVnInfoBackend/AnimeVnInfoBackend.Model/AnimeVnInfoBackend.Model.csproj", "AnimeVnInfoBackend/AnimeVnInfoBackend.Model/"]
COPY ["AnimeVnInfoBackend/AnimeVnInfoBackend.Repository/AnimeVnInfoBackend.Repository.csproj", "AnimeVnInfoBackend/AnimeVnInfoBackend.Repository/"]
COPY ["AnimeVnInfoBackend/AnimeVnInfoBackend.Service/AnimeVnInfoBackend.Service.csproj", "AnimeVnInfoBackend/AnimeVnInfoBackend.Service/"]
COPY ["AnimeVnInfoBackend/AnimeVnInfoBackend.Utility/AnimeVnInfoBackend.Utility.csproj", "AnimeVnInfoBackend/AnimeVnInfoBackend.Utility/"]
COPY ["AnimeVnInfoBackend/AnimeVnInfoBackend.View/AnimeVnInfoBackend.View.csproj", "AnimeVnInfoBackend/AnimeVnInfoBackend.View/"]
RUN dotnet restore "./AnimeVnInfoBackend/AnimeVnInfoBackend/AnimeVnInfoBackend.csproj"
COPY . .
WORKDIR "/src/AnimeVnInfoBackend/AnimeVnInfoBackend"

FROM build AS publish
ARG BUILD_CONFIGURATION=Release
RUN dotnet publish "./AnimeVnInfoBackend.csproj" -c $BUILD_CONFIGURATION -o /app/publish /p:UseAppHost=false

FROM base AS final
WORKDIR /app
COPY --from=publish --chown=app:app /app/publish .
RUN mkdir /app/Image
RUN mkdir /app/Logs
ENTRYPOINT ["dotnet", "AnimeVnInfoBackend.dll"]

there nothing other than build command

Unknown User•2mo ago

Message Not Public

Keswiik•2mo ago

assuming he actually ran docker compose build, there is no reason for services to come up

Unknown User•2mo ago

Message Not Public

Keswiik•2mo ago

it's just creating and tagging images, not starting containers

A Ka SupOP•2mo ago

:sadge: please wait me reinstall docker desktop, then you can understand what the point

Unknown User•2mo ago

Message Not Public

Keswiik•2mo ago

you don't need docker desktop for the sake of me and tebs sanity, run a build with that progress flag we could have logs by now lol

A Ka SupOP•2mo ago

its running, how to send

Keswiik•2mo ago

copy from your console if it gets stuck for a while

Unknown User•2mo ago

Message Not Public

Keswiik•2mo ago

or re-run the build and pipe it to a text file that you can easily copy / paste from

Unknown User•2mo ago

Message Not Public

A Ka SupOP•2mo ago

then wait me around 25mins

Unknown User•2mo ago

Message Not Public

A Ka SupOP•2mo ago

:kekw: oops i forgot i have to go to sleep after 25mins

Unknown User•2mo ago

Message Not Public

A Ka SupOP•2mo ago

yeah, i see all of them are run in parallel

Unknown User•2mo ago

Message Not Public

A Ka SupOP•2mo ago

PS D:\AnimeVnInfo> docker compose build --progress=plain | logs.txt logs.txt : The term 'logs.txt' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:41 + docker compose build --progress=plain | logs.txt + ~~~~ + CategoryInfo : ObjectNotFound: (logs.txt:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException oh no

Unknown User•2mo ago

Message Not Public

A Ka SupOP•2mo ago

yeah, running now

Unknown User•2mo ago

Message Not Public

A Ka SupOP•2mo ago

:kekw: but i can't wait till it finish, i have to go to sleep now, it's 23:35 here

Unknown User•2mo ago

Message Not Public

Keswiik•2mo ago

https://devblogs.microsoft.com/powershell-community/how-to-send-output-to-a-file/ rather slow, but google is also your friend

Unknown User•2mo ago

Message Not Public

Keswiik•2mo ago

it should, but figured i'd throw in the 'powershell' way of doing things too

A Ka SupOP•2mo ago

whoa, this still not done yet, i need to run the build again

Keswiik•2mo ago

or check if the log file has logs in it and if it does, send them

A Ka SupOP•2mo ago

i created new logs file here, this is at version 4.43.1

A Ka SupOP•2mo ago

logs_4.43.1.txt

A Ka SupOP•2mo ago

version 4.33.1 one

logs_4.33.1.txt

A Ka SupOP•2mo ago

this is log file that i cancelled, i dont understand why it stuck

logs_bugs.txt

A Ka SupOP•2mo ago

you can see both version 4.33 and 4.43 are super different

Keswiik•2mo ago

well it looks like animuvn-info gets stuck loading its build context

A Ka SupOP•2mo ago

stuck for 8 hours, no way

Keswiik•2mo ago

it's what the logs show ¯\_(ツ)_/¯ towards the end of your log file it's sent nearly 3gb of 'build context' to the docker daemon

#10 [animuvn-info internal] load build context
#10 transferring context: 2.61GB 90.4s

#10 [animuvn-info internal] load build context
#10 transferring context: 2.61GB 90.4s

A Ka SupOP•2mo ago

what, i dont know it's transferring to where

Keswiik•2mo ago

....to the docker daemon, like i just said

A Ka SupOP•2mo ago

:kekw: okay, let me google what is docker daemon

Keswiik•2mo ago

the actual docker service running on your pc that hosts the images and runs containers compose is just a CLI tool, it has to send info to the docker service on your PC to do anything

A Ka SupOP•2mo ago

okay, nvm, but as i said the build runs simultaneously at version 4.43.1

Keswiik•2mo ago

i don't care

A Ka SupOP•2mo ago

this makes slow the build

Keswiik•2mo ago

i am diagnosing your build issues i don't care how docker behaved previously what is the size of your AnimeVnInfoFrontend folder?

A Ka SupOP•2mo ago

included node_modules?

Keswiik•2mo ago

yes

A Ka SupOP•2mo ago

Keswiik•2mo ago

yeah, i'm guessing that's your issue are you using a .dockerignore to prevent it from sending unneeded files to the daemon? what kind of front end is this?

A Ka SupOP•2mo ago

dockerignore

A Ka SupOP•2mo ago

**/.classpath
**/.dockerignore
**/.env
**/.git
**/.gitignore
**/.project
**/.settings
**/.toolstarget
**/.vs
**/.vscode
**/*.*proj.user
**/*.dbmdl
**/*.jfm
**/azds.yaml
**/bin
**/charts
**/docker-compose*
**/Dockerfile*
**/node_modules
**/npm-debug.log
**/obj
**/secrets.dev.yaml
**/values.dev.yaml
LICENSE
README.md
!**/.gitignore
!.git/HEAD
!.git/config
!.git/packed-refs
!.git/refs/heads/**
__pycache__
.git
*.pyc
*.log

**/.classpath
**/.dockerignore
**/.env
**/.git
**/.gitignore
**/.project
**/.settings
**/.toolstarget
**/.vs
**/.vscode
**/*.*proj.user
**/*.dbmdl
**/*.jfm
**/azds.yaml
**/bin
**/charts
**/docker-compose*
**/Dockerfile*
**/node_modules
**/npm-debug.log
**/obj
**/secrets.dev.yaml
**/values.dev.yaml
LICENSE
README.md
!**/.gitignore
!.git/HEAD
!.git/config
!.git/packed-refs
!.git/refs/heads/**
__pycache__
.git
*.pyc
*.log

i place it at same folder with docker-compose file

Keswiik•2mo ago

i assume something unintended is happening with the dockerignore you have and extra stuff is being sent https://stackoverflow.com/questions/38946683/how-to-test-dockerignore-file you might be able to use some of the suggestions here to test it and see

A Ka SupOP•2mo ago

i think it works because i saw my images size is small

A Ka SupOP•2mo ago

Keswiik•2mo ago

not everything in the build context is copied into the image it's just the build context

A Ka SupOP•2mo ago

this is at my hub

Keswiik•2mo ago

show your dockerfile

A Ka SupOP•2mo ago

# syntax=docker.io/docker/dockerfile:1

FROM node:24-alpine AS base

# Install dependencies only when needed
FROM base AS deps
# Check https://github.com/nodejs/docker-node/tree/b4117f9333da4138b03a546ec926ef50a31506c3#nodealpine to understand why libc6-compat might be needed.
RUN apk add --no-cache libc6-compat
WORKDIR /app

# Install dependencies based on the preferred package manager
COPY ["AnimeVnInfoFrontend/package.json", "AnimeVnInfoFrontend/"]
COPY ["AnimeVnInfoFrontend/package-lock.json", "AnimeVnInfoFrontend/"]
WORKDIR "/app/AnimeVnInfoFrontend"
RUN npm i

# Rebuild the source code only when needed
FROM base AS builder
WORKDIR /app
COPY --from=deps /app/AnimeVnInfoFrontend/node_modules ./AnimeVnInfoFrontend/node_modules
COPY . .

# Next.js collects completely anonymous telemetry data about general usage.
# Learn more here: https://nextjs.org/telemetry
# Uncomment the following line in case you want to disable telemetry during the build.
# ENV NEXT_TELEMETRY_DISABLED=1
WORKDIR "/app/AnimeVnInfoFrontend"
RUN npm run build

# Production image, copy all the files and run next
FROM base AS runner
WORKDIR /app

ENV NODE_ENV=production
# Uncomment the following line in case you want to disable telemetry during runtime.
# ENV NEXT_TELEMETRY_DISABLED=1

RUN addgroup --system --gid 1001 nodejs
RUN adduser --system --uid 1001 nextjs

COPY --from=builder /app/AnimeVnInfoFrontend/public ./public

# Automatically leverage output traces to reduce image size
# https://nextjs.org/docs/advanced-features/output-file-tracing
COPY --from=builder --chown=nextjs:nodejs /app/AnimeVnInfoFrontend/.next/standalone ./
COPY --from=builder --chown=nextjs:nodejs /app/AnimeVnInfoFrontend/.next/static ./.next/static

USER nextjs

EXPOSE 3000

ENV PORT=3000

# server.js is created by next build from the standalone output
# https://nextjs.org/docs/pages/api-reference/config/next-config-js/output
ENV HOSTNAME="0.0.0.0"
CMD ["node", "server.js"]

# syntax=docker.io/docker/dockerfile:1

FROM node:24-alpine AS base

# Install dependencies only when needed
FROM base AS deps
# Check https://github.com/nodejs/docker-node/tree/b4117f9333da4138b03a546ec926ef50a31506c3#nodealpine to understand why libc6-compat might be needed.
RUN apk add --no-cache libc6-compat
WORKDIR /app

# Install dependencies based on the preferred package manager
COPY ["AnimeVnInfoFrontend/package.json", "AnimeVnInfoFrontend/"]
COPY ["AnimeVnInfoFrontend/package-lock.json", "AnimeVnInfoFrontend/"]
WORKDIR "/app/AnimeVnInfoFrontend"
RUN npm i

# Rebuild the source code only when needed
FROM base AS builder
WORKDIR /app
COPY --from=deps /app/AnimeVnInfoFrontend/node_modules ./AnimeVnInfoFrontend/node_modules
COPY . .

# Next.js collects completely anonymous telemetry data about general usage.
# Learn more here: https://nextjs.org/telemetry
# Uncomment the following line in case you want to disable telemetry during the build.
# ENV NEXT_TELEMETRY_DISABLED=1
WORKDIR "/app/AnimeVnInfoFrontend"
RUN npm run build

# Production image, copy all the files and run next
FROM base AS runner
WORKDIR /app

ENV NODE_ENV=production
# Uncomment the following line in case you want to disable telemetry during runtime.
# ENV NEXT_TELEMETRY_DISABLED=1

RUN addgroup --system --gid 1001 nodejs
RUN adduser --system --uid 1001 nextjs

COPY --from=builder /app/AnimeVnInfoFrontend/public ./public

# Automatically leverage output traces to reduce image size
# https://nextjs.org/docs/advanced-features/output-file-tracing
COPY --from=builder --chown=nextjs:nodejs /app/AnimeVnInfoFrontend/.next/standalone ./
COPY --from=builder --chown=nextjs:nodejs /app/AnimeVnInfoFrontend/.next/static ./.next/static

USER nextjs

EXPOSE 3000

ENV PORT=3000

# server.js is created by next build from the standalone output
# https://nextjs.org/docs/pages/api-reference/config/next-config-js/output
ENV HOSTNAME="0.0.0.0"
CMD ["node", "server.js"]

Keswiik•2mo ago

what kind of frontend are you using?

A Ka SupOP•2mo ago

nextjs

Keswiik•2mo ago

so react

A Ka SupOP•2mo ago

so is's transfering to daemon at COPY . . ?

Keswiik•2mo ago

dude it transfers everything in the build folder that isn't ignored by your .dockerignore to the daemon that is what i keep trying to tell you your logs show that is has transferred nearly 3gb of context, which is a lot

A Ka SupOP•2mo ago

yeah i checked my WSL disk over 35GB just only one run

Keswiik•2mo ago

so i would assume there's something going on with your dockerignore

A Ka SupOP•2mo ago

so it should be place at where?

Keswiik•2mo ago

looking at your 4.33.1 logs, you can see the context is much smaller

#60 [animuvn-info internal] load build context
#60 transferring context: 652.97kB 4.7s done
#60 DONE 5.5s

#60 [animuvn-info internal] load build context
#60 transferring context: 652.97kB 4.7s done
#60 DONE 5.5s

A Ka SupOP•2mo ago

yeah, because i reinstall the docker

Keswiik•2mo ago

is english your second language or something? i feel like there is a language barrier

A Ka SupOP•2mo ago

it's not my mother language sometims i need google translate

Keswiik•2mo ago

4.33.1 context size: 652.97kB 4.43 context size: 2.6GB+ something is causing docker to mess up its build context in 4.43

A Ka SupOP•2mo ago

can you explain what it is transferring?

#5 [api-animuvn-info-admin internal] load build context
#5 transferring context: 1.88GB 50.9s
#5 transferring context: 2.09GB 56.1s
#5 transferring context: 2.31GB 61.1s
#5 transferring context: 2.52GB 66.2s
#5 transferring context: 2.73GB 71.2s
#5 transferring context: 2.92GB 76.3s
#5 transferring context: 3.12GB 81.4s
#5 transferring context: 3.31GB 86.4s
#5 transferring context: 3.52GB 91.4s
#5 transferring context: 3.72GB 96.4s
#5 transferring context: 3.93GB 101.5s
#5 transferring context: 4.11GB 106.6s
#5 transferring context: 4.28GB 111.7s
#5 transferring context: 4.49GB 116.7s
#5 transferring context: 4.68GB 121.8s
#5 transferring context: 4.89GB 126.9s
#5 transferring context: 5.09GB 132.0s
#5 transferring context: 5.29GB 137.1s
#5 transferring context: 5.48GB 142.3s
#5 transferring context: 5.68GB 147.3s
#5 transferring context: 5.88GB 152.4s
#5 transferring context: 6.07GB 157.4s
#5 transferring context: 6.26GB 162.4s
#5 transferring context: 6.46GB 167.4s
#5 transferring context: 6.65GB 172.4s
#5 transferring context: 6.78GB 177.4s
#5 transferring context: 6.90GB 182.5s
#5 transferring context: 7.08GB 187.5s
#5 transferring context: 7.25GB 192.5s
#5 transferring context: 7.45GB 197.6s
#5 transferring context: 7.59GB 201.6s done
#5 DONE 202.3s

#5 [api-animuvn-info-admin internal] load build context
#5 transferring context: 1.88GB 50.9s
#5 transferring context: 2.09GB 56.1s
#5 transferring context: 2.31GB 61.1s
#5 transferring context: 2.52GB 66.2s
#5 transferring context: 2.73GB 71.2s
#5 transferring context: 2.92GB 76.3s
#5 transferring context: 3.12GB 81.4s
#5 transferring context: 3.31GB 86.4s
#5 transferring context: 3.52GB 91.4s
#5 transferring context: 3.72GB 96.4s
#5 transferring context: 3.93GB 101.5s
#5 transferring context: 4.11GB 106.6s
#5 transferring context: 4.28GB 111.7s
#5 transferring context: 4.49GB 116.7s
#5 transferring context: 4.68GB 121.8s
#5 transferring context: 4.89GB 126.9s
#5 transferring context: 5.09GB 132.0s
#5 transferring context: 5.29GB 137.1s
#5 transferring context: 5.48GB 142.3s
#5 transferring context: 5.68GB 147.3s
#5 transferring context: 5.88GB 152.4s
#5 transferring context: 6.07GB 157.4s
#5 transferring context: 6.26GB 162.4s
#5 transferring context: 6.46GB 167.4s
#5 transferring context: 6.65GB 172.4s
#5 transferring context: 6.78GB 177.4s
#5 transferring context: 6.90GB 182.5s
#5 transferring context: 7.08GB 187.5s
#5 transferring context: 7.25GB 192.5s
#5 transferring context: 7.45GB 197.6s
#5 transferring context: 7.59GB 201.6s done
#5 DONE 202.3s

at version 4.33 no, this is backend, net core api

A Ka SupOP•2mo ago

i run the build again at version 4.33, seems like 7.59GB things transferred above is from NET Core itself

logs2.txt

Gaming

Programming

Docker build time is too big

Did you find this page helpful?