Where does the current image's size and build time actually go? Build the current Dockerfile
locally and get a layer-by-layer breakdown (docker history, docker build timing per step) that
separates: (a) the barichello/godot-ci base image itself, (b) the apt-get install layer (build
toolchain, mingw-w64, X11/audio dev libs), (c) the Blender download/extract layer.
Report concrete numbers (MB per layer, seconds per step) — this is the evidence the approach
decision (grilling ticket, blocked on this + the research tickets) weighs against.
## Question
Where does the current image's size and build time actually go? Build the current `Dockerfile`
locally and get a layer-by-layer breakdown (`docker history`, `docker build` timing per step) that
separates: (a) the `barichello/godot-ci` base image itself, (b) the `apt-get install` layer (build
toolchain, mingw-w64, X11/audio dev libs), (c) the Blender download/extract layer.
Report concrete numbers (MB per layer, seconds per step) — this is the evidence the approach
decision (grilling ticket, blocked on this + the research tickets) weighs against.
Part of [Smaller/faster godot-ci image (map)](https://git.arthurerlich.de/haylan/godot-ci/issues/2).
Superseded — the size/build-time measurement this ticket asked for got captured directly while resolving ticket #7 instead of as a separate session (barichello/godot-ci's bare base = 2460MB vs. the new debian:bookworm-slim image's full 2343MB, both measured via real docker build/run). Closing without a separate layer-by-layer breakdown since the decision it was meant to inform is already made and verified.
Superseded — the size/build-time measurement this ticket asked for got captured directly while resolving [ticket #7](https://git.arthurerlich.de/haylan/godot-ci/issues/7) instead of as a separate session (barichello/godot-ci's bare base = 2460MB vs. the new debian:bookworm-slim image's full 2343MB, both measured via real docker build/run). Closing without a separate layer-by-layer breakdown since the decision it was meant to inform is already made and verified.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Question
Where does the current image's size and build time actually go? Build the current
Dockerfilelocally and get a layer-by-layer breakdown (
docker history,docker buildtiming per step) thatseparates: (a) the
barichello/godot-cibase image itself, (b) theapt-get installlayer (buildtoolchain, mingw-w64, X11/audio dev libs), (c) the Blender download/extract layer.
Report concrete numbers (MB per layer, seconds per step) — this is the evidence the approach
decision (grilling ticket, blocked on this + the research tickets) weighs against.
Part of Smaller/faster godot-ci image (map).
Superseded — the size/build-time measurement this ticket asked for got captured directly while resolving ticket #7 instead of as a separate session (barichello/godot-ci's bare base = 2460MB vs. the new debian:bookworm-slim image's full 2343MB, both measured via real docker build/run). Closing without a separate layer-by-layer breakdown since the decision it was meant to inform is already made and verified.