Skip to content
SHC Docs

GitLab

These answers used to sit on this app’s store listing. They moved here on 2026-08-17: a shopper deciding whether to install is not reading six hundred words of Q&A, and the listing page is the pitch. The knowledge is no less true for being off the storefront: it is the part you want before you commit, which is what a guide is for.

Yes. The package installs the GitLab CE image and tracks its releases. Everything described on this page is CE behaviour.

No. Single sign-on is optional and inert until an OIDC integration is attached. Without one you get the root account and GitLab’s own user management. With one, signing out ends the identity provider’s session too, so a user who signs out stays signed out.

18.11 is a required stop on GitLab’s own documented upgrade path between 18.10 and 19.x. Moving past it is a staged migration rather than a version-pin edit, so the package parks there on purpose instead of jumping a rung and stranding your data.

Yes. Artifacts, LFS objects, packages, Pages, uploads and the rest live in S3 buckets, and the install is refused without an s3 integration or vars.s3.endpoint. SHC ships no S3 server of its own: make the buckets at a hosted provider (Backblaze B2, Hetzner Object Storage, Cloudflare R2 or any S3-compatible service) and bind the s3 plug to an s3 connection, directly or through an external-s3 front. See Object storage for apps.

Does the container registry go to object storage too?

Section titled “Does the container registry go to object storage too?”

No. Registry blobs stay on the stack’s own disk (GitLab’s omnibus packaging uses the filesystem driver for them), and the backup accounts for that explicitly. Artifacts, LFS, packages, Pages and the rest do go to the buckets.

The database names an object in a bucket for every row of the nine types in app.yaml’s vars.s3.objects table. vars.s3.bucket sets the base name; each bucket is <bucket>-<suffix>, with its suffix from vars.s3.objects.

TypeWhat it holds
artifactsCI job artifacts, including archived job logs
ci_secure_filesCI secure files
dependency_proxyDependency proxy cache
external_diffsMerge-request diffs stored outside the database
lfsGit LFS objects
packagesPackage registry
pagesGitLab Pages content
terraform_stateTerraform state files
uploadsUser uploads, including avatars and attachments

The container registry stays on the gitlab-data volume by default. With vars.s3.registry on, it uses <bucket>-registry instead. Include that bucket when the setting is on.

A move carries the database whole. Carry every one of those buckets, including ones that look empty. Copy without overwrites or deletes, then prove each bucket with rclone check --one-way before the flip. Substitute your configured remotes and bucket names, and repeat for each bucket:

Terminal window
rclone copy --immutable source:SOURCE_BUCKET destination:DESTINATION_BUCKET
rclone check --one-way source:SOURCE_BUCKET destination:DESTINATION_BUCKET

If you deliberately leave a type behind, remove that type’s rows in the same window. Otherwise GitLab lists objects it can’t serve: an old job log shows at its old size with nothing in it, and old artifact downloads 404. This can go unnoticed with no error anywhere else.

After a restore, the post_restore job gitlab-object-check runs GitLab’s verifiers over a sample of each of the four types they support: artifacts, LFS objects, uploads and CI secure files. It checks up to 200 rows per type, spread across the ID range, and checks tables of 200 rows or fewer whole. The restore fails when a sampled row has no object or a check can’t finish. Run it again any time:

Terminal window
shc job run gitlab-object-check --stack gitlab --wait

The verifiers check one object at a time. At about 180 ms per row measured, a full pass over 88,888 artifacts takes about 4.4 hours. When you can wait, run the full per-row checks inside the gitlab container:

Terminal window
gitlab-rake gitlab:artifacts:check
gitlab-rake gitlab:lfs:check
gitlab-rake gitlab:uploads:check
gitlab-rake gitlab:ci_secure_files:check

The sample catches missing or unreadable buckets; it doesn’t prove a copy is complete. The move isn’t done until the rclone checks and gitlab-object-check pass.