Self-host GitLab CE with Levelrail
A complete DevOps platform for source control, code review, issues, and CI/CD in one place.
- Memory4 GiB
- Archarm64
- Services1
How to self-host GitLab CE
-
Pull the images
One image is pulled on your server.
Show images
gitlab/gitlab-ce:19.3.1-ce.0
-
Create the app
One service starts in a single Compose app, with 3 named volume mounts for your data, on port 80.
-
Fill in the secrets
1 setting is preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
GitLab CE requirements
- Memory
- About 4 GiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 80
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- not yet recorded
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 80 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then GitLab CE. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the GitLab CE docs page.
Deploy GitLab CE your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy GitLab CE from the CLI
levelrail-cli templates deploy gitlab-ce --name my-gitlab-ce Deploy GitLab CE with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/gitlab-ce/deploy GitLab CE configuration
GitLab CE services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| gitlab | gitlab/gitlab-ce:19.3.1-ce.0 | 80 | gitlab_config -> /etc/gitlabgitlab_logs -> /var/log/gitlabgitlab_data -> /var/opt/gitlab |
GitLab CE environment variables
| Variable | Service | Value |
|---|---|---|
| GITLAB_OMNIBUS_CONFIG | gitlab | Preset by the template |
Ports and volumes
- Ports
- 80
- Volumes
- 3 named mounts: gitlab_config -> /etc/gitlab, gitlab_logs -> /var/log/gitlab, gitlab_data -> /var/opt/gitlab
GitLab CE FAQ
How much memory does GitLab CE need?
The catalog lists about 4 GiB of memory for GitLab CE.
Does GitLab CE run on arm64?
For GitLab CE, an arm64 image is published; amd64 is image published.
Does GitLab CE need configuration before it starts?
No. The template fills in its own defaults.
Which ports does GitLab CE use?
GitLab CE listens on port 80 inside the stack.
Where does GitLab CE keep its data?
In named volumes: gitlab_config mounted at /etc/gitlab, gitlab_logs mounted at /var/log/gitlab and gitlab_data mounted at /var/opt/gitlab.
Can I deploy GitLab CE on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id gitlab-ce for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image gitlab/gitlab-ce:19.3.1-ce.0 is what you deploy there.