Chainguard Image for opensearch-dashboards

Minimal image with OpenSearch Dashboards

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/opensearch-dashboards:latest

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

Using OpenSearch Dashboards

Chainguard OpenSearch images include the opensearch package and helper scripts which can be used to start up or configure OpenSearch.

The full list of included tools is:

$ ls /usr/share/opensearch-dashboards/bin/
opensearch-dashboards      opensearch-dashboards-plugin      opensearch-dashboards-keystore      use_node

The default entrypoint is set to run the included /usr/share/opensearch-dashboards/opensearch-dashboards-docker-entrypoint.sh script.

To get started:

Install OpenSearch and then OpenSearch Dashboards.

1. Add the OpenSearch Helm Repository

helm repo add opensearch https://opensearch-project.github.io/helm-charts

2. Create Your Custom OpenSearch Values File

Create a custom values file to specify the configuration for your OpenSearch deployment. Below are the contents you'll use for this example. Copy the following configuration into a file named values-opensearch.yaml.

singleNode: true # useful for single node testing
majorVersion: "2"
image:
  repository: cgr.dev/chainguard/opensearch
  tag: latest

3. Install OpenSearch with Helm Now, you're ready to install OpenSearch using the Helm chart and your custom values file. Run the following command to start the deployment:

helm install opensearch opensearch/opensearch -f values-opensearch.yaml

4. Create Your Custom OpenSearch Dashboard Values File values-opensearch-dashboard.yaml.

singleNode: true
majorVersion: "2"
image:
  repository: cgr.dev/chainguard/opensearch-dasboards
  tag: latest
startupProbe:
  timeoutSeconds: 10
  initialDelaySeconds: 20

5. Install OpenSearch Dasboards with Helm

helm install opensearch-dashboards opensearch/opensearch-dashboards  -f values-opensearch-dashboard.yaml

6. Access the UI using an ingress controller or kubectl port-forward

kubectl port-forward svc/opensearch-dashboards 5601:5601

7. Access the Dashboard

Visit http://localhost:5601

8. Login in

Using default setup credentials admin/admin

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:

• Minimal design, with no unnecessary software bloat
• Automated nightly builds to ensure Images are completely up-to-date and contain all available security patches
• High quality build-time SBOMs (software bills of materials) attesting the provenance of all artifacts within the Image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

-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.