Skip to main content

Registries

WUD inspects remote container registries to discover image tags, digest hashes, and semver updates for your monitored containers.

How WUD Resolves Registries

When WUD monitors a container (e.g. redis:7-alpine or ghcr.io/owner/app:1.2.0), it parses the image name to detect the target registry domain automatically.


Request Throttling

WUD limits requests independently for each configured registry instance. Requests above the limit wait in FIFO order, so one registry cannot consume the capacity of another.

WUD_REGISTRY_{REGISTRY_TYPE}_{REGISTRY_NAME}_CONCURRENCY
Optionalintegerdefault: 2

Maximum number of active requests for this registry instance. An invalid value prevents the registry from registering.

Allowed values:Any integer greater than or equal to 1

When a registry returns HTTP 429, WUD retries twice. It honors Retry-After values up to 60 seconds; otherwise it waits for a jittered 1–2 seconds before the first retry and 2–4 seconds before the second. Request slots are released during these delays. Longer retry windows are deferred to the next normal scan, and non-429 failures are not retried.

Retry timing is fixed and is not separately configurable.


⚡ Active by Default (Zero-Config for Public Images)

These registries work out of the box with zero configuration for public images.

You only need to configure environment variables if you want to:

  • Access private repositories
  • Increase API rate limits (e.g. Docker Hub authenticated tier)
  • Connect to a self-hosted instance (e.g. on-premise Forgejo or Quay)

Alibaba Cloud (ACR)

⚡ Active by Default

Monitors public images on Alibaba Cloud Container Registry (*.aliyuncs.com) anonymously.

AWS ECR Public

⚡ Active by Default

Monitors public images hosted on Amazon ECR Public Gallery anonymously without AWS credentials.

Codeberg

⚡ Active by Default

Public Codeberg images supported anonymously. Configure access tokens for private packages.

DigitalOcean (DOCR)

⚡ Active by Default

Monitors public repositories on DigitalOcean Container Registry anonymously out of the box.

Docker Hub

⚡ Active by Default

Monitors public images anonymously by default. Configure username and PAT/password for private repos or increased rate limits.

Forgejo

⚡ Active by Default

Public images on code.forgejo.org supported anonymously. Configure instance URL and tokens for self-hosted Forgejo.

GitHub Container Registry (GHCR)

⚡ Active by Default

Monitors public packages anonymously out of the box. Configure a GitHub Personal Access Token (PAT) for private packages.

GitLab

⚡ Active by Default

Monitors public images anonymously on registry.gitlab.com by default. Configure a GitLab Personal Access Token for private repositories or self-hosted instances.

Google Container Registry (GCR)

⚡ Active by Default

Public images supported anonymously. Configure a Google Service Account JSON key for private images and Artifact Registry.

IBM Cloud (ICR)

⚡ Active by Default

Monitors public namespaces on IBM Cloud Container Registry (*.icr.io) anonymously.

JFrog Artifactory

⚡ Active by Default

Monitors public images hosted on JFrog Cloud (*.jfrog.io) anonymously.

LinuxServer (LSCR)

⚡ Active by Default

Seamless tag and update monitoring for the entire LinuxServer.io container ecosystem.

Oracle Cloud (OCIR)

⚡ Active by Default

Monitors public images on Oracle Cloud Infrastructure Registry (*.ocir.io) anonymously.

Quay

⚡ Active by Default

Red Hat Quay public images supported anonymously. Supports custom tokens for private repos and on-prem Quay clusters.

Scaleway

⚡ Active by Default

Monitors public namespaces on Scaleway Container Registry (rg.<region>.scw.cloud) anonymously.

TrueForge

⚡ Active by Default

Public TrueForge OCI image registry support out of the box.


🔐 Dedicated Setup Required

These registries host private images or custom infrastructure and require explicit credentials or endpoint configuration before WUD can monitor your containers.