wazuh-dashboard

packaged by Chainguard

Chainguard Container for wazuh-dashboard

Wazuh is a free and open source security platform that provides XDR and SIEM features to protect your cloud, container, and server workloads.

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/wazuh-dashboard:latest

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

Compatibility Notes

Chainguard's Wazuh images are compatible with the upstream Wazuh project and can be used as drop-in replacements in standard Wazuh deployments.

Wazuh Dashboard Compatibility

The Chainguard wazuh-dashboard image is similar to the upstream wazuh/wazuh-dashboard image but enforces stricter user and group permissions following the principle of least privilege. The application user is granted ownership only over the files and directories required at runtime, while all other paths remain owned by root.

Available Images

The Wazuh stack is composed of multiple components. Currently, the following Chainguard image is available:

• wazuh-dashboard

cgr.dev/ORGANIZATION/wazuh-dashboard:latest

The wazuh-dashboard component provides the web-based interface for visualizing, analyzing, and managing security data.

Getting Started

Chainguard Wazuh images integrate with standard deployment workflows. Deployments follow the upstream Wazuh process, with image overrides applied during setup.

Replace <version> with the desired Wazuh release (for example, v4.x.y).

Docker Deployment

This deployment builds on the Wazuh Docker deployment guide, applying Chainguard image overrides during setup.

Setup

To use the official Wazuh Docker Compose deployment, clone the wazuh-docker repository:

git clone https://github.com/wazuh/wazuh-docker.git -b <version>
cd wazuh-docker/single-node/

Generate certificates as described in the certificate deployment guide.

Override Images

Create a docker-compose.override.yml file:

services:
  wazuh.dashboard:
    image: cgr.dev/ORGANIZATION/wazuh-dashboard:<version>

Deploy

docker-compose -f docker-compose.yml -f docker-compose.override.yml up -d

Verify Deployment

If your deployment is successful, you can access the Wazuh dashboard at https://<DOCKER_HOST_IP> using the default credentials documented in the Wazuh Docker guide.

Kubernetes Deployment

This deployment builds on the Wazuh Kubernetes deployment guide, using the local cluster (envs/local-env) configuration with image overrides applied via kustomize.

Setup

To use the official Wazuh Kubernetes deployment, clone the wazuh-kubernetes repository:

git clone https://github.com/wazuh/wazuh-kubernetes.git -b <version> --depth=1
cd wazuh-kubernetes

Generate certificates:

wazuh/certs/indexer_cluster/generate_certs.sh
wazuh/certs/dashboard_http/generate_certs.sh

Override Images

Update your kustomization (for example, envs/local-env/kustomization.yaml):

images:
  - name: wazuh/wazuh-dashboard
    newName: cgr.dev/ORGANIZATION/wazuh-dashboard
    newTag: <version>

Deploy

kubectl apply -k envs/local-env/

Verify Deployment

You can verify that all components are running correctly by checking the status of deployments and pods in the wazuh namespace.

kubectl get deployments -n wazuh

Example output:

NAME             READY   UP-TO-DATE   AVAILABLE   AGE
wazuh-dashboard  1/1     1            1           11m

kubectl get pods -n wazuh

Example output:

NAME                              READY   STATUS    RESTARTS   AGE
wazuh-indexer-0                   1/1     Running   0          15m
wazuh-dashboard-xxxxx             1/1     Running   0          14m
wazuh-manager-master-0            1/1     Running   0          12m
wazuh-manager-worker-0-0          1/1     Running   0          11m
wazuh-manager-worker-1-0          1/1     Running   0          11m

All pods should be in the Running state.

You can verify that the Wazuh dashboard is running by retrieving the external IP of the dashboard service:

kubectl get services -o wide -n wazuh

Example output:

NAME        TYPE           CLUSTER-IP       EXTERNAL-IP        PORT(S)                      AGE
dashboard   LoadBalancer   xxx.xx.xxx.xxx   xxx.xx.xxx.xxx     80:31831/TCP,443:30974/TCP   15m

The Wazuh dashboard will be available at https://<EXTERNAL-IP>, and can be accessed with the default credentials documented in the Wazuh Kubernetes guide.

Documentation and Resources

• Wazuh GitHub Repository
• Wazuh Documentation
• Docker Deployment Guide
• Kubernetes Deployment Guide

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.