Skip to main content

GitLab Container Registry

⚡ Active by Default

The gitlab registry module authenticates against GitLab Container Registries (GitLab.com and self-hosted instances).

Zero-Config for Public Images

Public packages work out of the box with zero configuration. Configure this module to monitor private repositories or avoid anonymous rate limits.

⚙️ Configuration Variables​

WUD_REGISTRY_GITLAB_{registry_name}_TOKEN
Requiredstring

GitLab Personal Access Token or Deploy Token

Allowed values:Valid GitLab Personal Access Token, Deploy Token, or Project Access Token
WUD_REGISTRY_GITLAB_{registry_name}_AUTHURL
Optionalurldefault: https://gitlab.com

GitLab authentication base URL

Allowed values:Valid instance URL
WUD_REGISTRY_GITLAB_{registry_name}_URL
Optionalurldefault: https://registry.gitlab.com

GitLab Container Registry base URL

Allowed values:Valid registry URL
WUD_REGISTRY_GITLAB_{registry_name}_USERNAME
Optionalstring

Username (required when using a Group Access Token or Deploy Token)

🚀 Examples​

Authenticate with GitLab.com​

services:
  whatsupdocker:
    image: getwud/wud
    environment:
      - WUD_REGISTRY_GITLAB_LOCAL_TOKEN=glpat-xxxxxxxxxxxxxxxxxxxx

Authenticate with a Self-Hosted GitLab Instance​

services:
  whatsupdocker:
    image: getwud/wud
    environment:
      - WUD_REGISTRY_GITLAB_LOCAL_URL=https://registry.gitlab.example.com
      - WUD_REGISTRY_GITLAB_LOCAL_AUTHURL=https://gitlab.example.com
      - WUD_REGISTRY_GITLAB_LOCAL_TOKEN=glpat-xxxxxxxxxxxxxxxxxxxx

📖 Setup Guide: Creating a GitLab Personal Access Token​

  1. Navigate to GitLab Personal Access Tokens.
  2. Select the read_registry scope (the only scope required by WUD).
  3. Click Create personal access token, copy the token string, and set it as WUD_REGISTRY_GITLAB_{registry_name}_TOKEN.