Skip to main content
Version: 9.x

Elastic Container Registry

⚡ Active by Default

The elastic registry module connects to Elastic Container Registry (docker.elastic.co).

Zero-Config for Public Images

Public images on docker.elastic.co (such as Elasticsearch, Kibana, and Logstash) work out of the box with zero configuration. WUD automatically negotiates the OCI anonymous Bearer token challenge. Configure credentials only when authenticating with private registries or custom mirrors.

⚙️ Configuration Variables​

WUD_REGISTRY_ELASTIC_{registry_name}_AUTH
Optionalstring

Base64-encoded credentials

Allowed values:Base64-encoded string (`username:password`)
WUD_REGISTRY_ELASTIC_{registry_name}_LOGIN
Optionalstring

Username / login for authenticated pulls

WUD_REGISTRY_ELASTIC_{registry_name}_PASSWORD
Optionalstring

Password for authenticated pulls

WUD_REGISTRY_ELASTIC_{registry_name}_TOKEN
Optionalstring

Bearer token for registry authentication

WUD_REGISTRY_ELASTIC_{registry_name}_URL
Optionalstringdefault: https://docker.elastic.co

Registry base URL

Allowed values:Valid HTTP/HTTPS registry URL

🚀 Examples​

Zero Configuration (Public Images)​

Because Elastic is active by default, monitoring containers such as docker.elastic.co/elasticsearch/elasticsearch:8.15.0 requires no environment variables at all.

Custom Elastic Mirror or Private Registry​

services:
  whatsupdocker:
    image: getwud/wud
    environment:
      - WUD_REGISTRY_ELASTIC_CUSTOM_URL=https://custom-elastic-mirror.example.com
      - WUD_REGISTRY_ELASTIC_CUSTOM_LOGIN=myuser
      - WUD_REGISTRY_ELASTIC_CUSTOM_PASSWORD=secretpassword