dhi.io/gitlab-workhorse
GitLab Workhorse
GitLab Workhorse is the smart reverse proxy that sits in front of GitLab, handling resource-intensive HTTP requests such as file uploads and downloads, Git operations, and archive downloads.
pushed 21 hours ago
linux/amd64, linux/arm64
324.75 MB
for linux/amd64
377
for linux/amd64
Active support
gitlab-workhorse, gitlab-resize-image, gitlab-zip-cat, gitlab-zip-metadata, exiftool
Build Level 3
Tamper-evident proof of how and from what sources this image was built. Build Level 3 is the highest the SLSA build track defines.
CycloneDX SBOM + SPDX SBOM
A software bill of materials in both CycloneDX and SPDX formats so it drops straight into your existing tooling. Audit exactly what you're shipping.
A Vulnerability Exploitability exchange document, Docker's assessment of which CVEs actually affect this image and which don't apply, so you can focus on real risk instead of chasing false positives.
Available
A link to everything used to build the image, package source code, Git repos, and build files, so you can audit or reproduce the build and stay compliant with open source licenses.
Every known vulnerability in this image, shown in full rather than hidden. The VEX data flags which ones actually apply, so you can tell real exposure from noise before you ship.
Exactly what changed in this build, down to the package bumps and fixes behind the version you're pulling.
Verifies no keys, tokens, or credentials were accidentally baked into the image.
The image layers were scanned for known malware signatures before publishing.
About GitLab Workhorse
GitLab Workhorse is a smart reverse proxy that sits in front of the GitLab Rails application. It handles resource-intensive HTTP requests that would otherwise tie up Rails workers — file uploads and downloads, Git operations over HTTP, and repository archive downloads — and streams them efficiently to and from object storage and Gitaly.
This is the Cloud Native GitLab (CNG) workhorse component, designed for Kubernetes and Docker Compose deployments where GitLab services run as separate containers. It is normally deployed alongside the GitLab Webservice (Puma) container, which it proxies via its configured authentication backend.
Like the upstream image, this image bundles the version-matched compiled GitLab Rails assets under /srv/gitlab/public,
allowing Workhorse to serve the web UI's CSS, JavaScript, fonts, and images directly. The upstream /srv/gitlab/doc
content is intentionally omitted because Workhorse does not require it.
For more information, visit the GitLab Workhorse documentation.
About Docker Hardened Images
Docker Hardened Images are built to meet the highest security and compliance standards. They provide a trusted foundation for containerized workloads by incorporating security best practices from the start.
Why use Docker Hardened Images?
These images are published with near-zero known CVEs, include signed provenance, and come with a complete Software Bill of Materials (SBOM) and VEX metadata. They're designed to secure your software supply chain while fitting seamlessly into existing Docker workflows.
Trademarks
GitLab is a trademark of GitLab Inc. in the United States and other countries and regions. All rights in the mark are reserved to GitLab Inc. Any use by Docker is for referential purposes only and does not indicate sponsorship, endorsement, or affiliation.