Portainer Templates logo

Portainer Templates

GitLab CE GitLab CE

Container

DevelopmentProject Management

Open-source end-to-end software development platform

Image details

Pulls: 386.0M
Architecture: amd64, arm64
Image size: 1.2 GB
Latest: 19.0.6-ce.0
User: gitlab
Created: Jul 10, 2015
Updated: 3 hours ago
Status: active

Configuration

Type
Container
Platform
linux
Image
gitlab/gitlab-ce:latest
Ports
80/tcp443/tcp22/tcp
Volumes
/etc/gitlab/var/log/gitlab/var/opt/gitlab

Template by portainer

Notes

Default username is root. Check the GitLab documentation to get started.

Standalone Install

Select an install method, to see config/commands for deploying GitLab CE

Installation method

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select GitLab CE, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo

More install options in our documentation.

GitLab Docker images

We don't monitor the comments here, if you need help with running this GitLab Docker image, please see https://about.gitlab.com/getting-help/

Serve GitLab CE on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.

Proxying gitlab-ce.example.com to http://gitlab-ce:80

Add this to your Caddyfile

gitlab-ce.example.com {
	reverse_proxy http://gitlab-ce:80
}

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs <container>
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Published on a random port

This template exposes 80/tcp without setting a host port, so Docker picks a random free one on every deploy.

  • Find it in the Ports column of Portainer's container list, or with docker port <container>

Image won't pull

Test the pull directly on the host: docker pull gitlab/gitlab-ce:latest

  • "manifest unknown" means the tag no longer exists. This template uses latest, so try pinning a specific version instead.
  • "toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
  • "no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

  • This image supports: amd64, arm64
  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

A single container

GitLab CE runs as one container, the simplest kind of app here. Just the one image to pull and nothing else wired up alongside it.

The app image

An image is the app packed up ready to go, everything GitLab CE needs bundled into one download. This template pulls gitlab/gitlab-ce:latest, which Docker fetches once (about 1.2 GB) and then starts your own copy from.

Where the image comes from

Docker pulls its images from registries, public libraries of ready-built apps. GitLab CE's comes from Docker Hub, published by gitlab.

Version tags

The bit after the colon in the image name is the version tag. Here it's latest, which always points at the newest build, so a redeploy can bump you to a newer release without you asking. Newest right now is 19.0.6-ce.0. Pin a specific tag if you would rather stay on one version.

Which machines it runs on

Every image is built for particular CPU types. This one ships for amd64, arm64, so it runs on both regular x86 servers and ARM boards like a Raspberry Pi.

Ports

A port is the door the app answers on. Here the app exposes a port but leaves the host side blank, so Docker picks a free one for you. It opens:

  • 80, published on a random host port
  • 443, published on a random host port
  • 22, published on a random host port

Volumes

A volume is where GitLab CE keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:

  • /etc/gitlab as a volume Docker manages for you
  • /var/log/gitlab as a volume Docker manages for you
  • /var/opt/gitlab as a volume Docker manages for you

Networking

Nothing custom is set, so GitLab CE sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.

Platform

The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set GitLab CE up. Add the template list to Portainer once, then deploying GitLab CE is a click rather than a wall of config.