Could the GitLab package be optimized to reduce its Docker image size?
-
The GitLab
19.3.2imagecloudron/com.gitlab.cloudronapp:202609150645580000occupies18.5 GBon my server, with16.1 GBreported as unique size. This is image storage, separate from repositories and other application data.docker historyshows these large layers:yarn install --production --pure-lockfile:5.08 GBGitalyand bundledGit build/install:4.40 GBWorkhorsecompilation:2.25 GBGitLab Shelldependencies and compilation:1.28 GB- Frontend asset compilation:
1.26 GB
The
GitLab Shellbuild also explicitly includes the development test Bundler groups.Would it be possible to review whether build caches, intermediate files and build-only dependencies could be excluded from the final image, using multi-stage builds or cleanup within the same build layer? Some of this may be required at runtime, so these figures are not necessarily reclaimable space.
Unused-image pruning is already complete. Reducing the installed image’s footprint would be helpful on servers running many Cloudron apps.
-
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login