DirectorySecurity Advisories
Sign In
Directory
gitlab-shell logo

gitlab-shell

Last changed

Sign In for Updates

Get notified of upcoming product changes, critical vulnerability notifications and patches and more.

Sign In
Versions
Overview
Provenance
Specifications
SBOM
Vulnerabilities
Advisories

Chainguard Image for gitlab-shell

Gitlab Shell

Chainguard Images are regularly-updated, minimal container images with low-to-zero CVEs.

Download this Image

This image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/gitlab-shell:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard registry.

Usage

Please refer to the following helm chart documentation for instructions on how to deploy GitLab in Kubernetes: see here.

The GitLab helm chart is composed of multiple sub-charts, one of which deploys the GitLab shell component.

Step 1: Pull down the source

The upstream Gitlab Helm repo contains custom values for deploying a compatible kind cluster, as well as values files for the helm chat to deploy with SSL disabled:

git clone https://gitlab.com/gitlab-org/charts/gitlab.git && cd gitlab

Step 2: Create new kind cluster#

This needs to be run from the root of the gitlab repo, step 1

kind create cluster --config examples/kind/kind-no-ssl.yaml

Step 3: Create default password

Creates a secret containing a default password for the root user, which we’ll need to pass into the helm chart:

kubectl create secret generic gitlab-gitlab-initial-root-password --from-literal=password='P@ssw3rd'

Step 4: Identify your public IP#

export MY_IP_ADDRESS=$(ipconfig getifaddr en0)

Step 5: Add the Gitlab helm repo#

helm repo add gitlab https://charts.gitlab.io/

Step 6: Deploy Gitlab helm chart!#

helm upgrade --install gitlab gitlab/gitlab \
  --set gitlab.gitlab-shell.image.repository=cgr.dev/chainguard-private/gitlab-shell \
  --set gitlab.gitlab-shell.image.repository=latest \
  --set global.hosts.domain=$MY_IP_ADDRESS.nip.io \
  --set gitlab.gitlab-root-password.secret=gitlab-gitlab-initial-root-password \
  -f examples/kind/values-base.yaml \
  -f examples/kind/values-no-ssl.yaml

Also, you can find the installation parameters related to the shell sub-chart here.

Contact Support

If you have a Zendesk account (typically set up for you by your Customer Success Manager) you can reach out to Chainguard's Customer Success team through our Zendesk portal.

What are Chainguard Images?

Chainguard Images are a collection of container images designed for security and minimalism.

Many Chainguard Images are distroless; they contain only an open-source application and its runtime dependencies. These images do not even contain a shell or package manager. Chainguard Images are built with Wolfi, our Linux undistro designed to produce container images that meet the requirements of a secure software supply chain.

The main features of Chainguard Images include:

-dev Variants

As mentioned previously, Chainguard’s distroless Images have no shell or package manager by default. This is great for security, but sometimes you need these things, especially in builder images. For those cases, most (but not all) Chainguard Images come paired with a -dev variant which does include a shell and package manager.

Although the -dev image variants have similar security features as their distroless versions, such as complete SBOMs and signatures, they feature additional software that is typically not necessary in production environments. The general recommendation is to use the -dev variants only to build the application and then copy all application artifacts into a distroless image, which will result in a final container image that has a minimal attack surface and won’t allow package installations or logins.

That being said, it’s worth noting that -dev variants of Chainguard Images are completely fine to run in production environments. After all, the -dev variants are still more secure than many popular container images based on fully-featured operating systems such as Debian and Ubuntu since they carry less software, follow a more frequent patch cadence, and offer attestations for what they include.

Learn More

To better understand how to work with Chainguard Images, we encourage you to visit Chainguard Academy, our documentation and education platform.

Licenses

Chainguard Images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" version of this image:

  • Apache-2.0

  • BSD-3-Clause

  • CC-PDDC

  • GCC-exception-3.1

  • GPL-2.0-only

  • GPL-2.0-or-later

  • GPL-3.0-or-later

For a complete list of licenses, please refer to this Image's SBOM.

Software license agreement

Compliance

A FIPS validated version of this image is available for FedRAMP compliance. STIG is included with FIPS image.


Related images

Safe Source for Open Sourceâ„¢
Media KitContact Us
© 2024 Chainguard. All Rights Reserved.
Private PolicyTerms of Use

Product

Chainguard Images