elasticvue

packaged by Chainguard

Chainguard Container for elasticvue

Elasticsearch GUI for browsers and as a self-hosted web app

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/elasticvue:latest

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

Compatibility Notes

This image is compatible with the upstream cars10/elasticvue image. It packages the Elasticvue single-page application served by nginx listening on port 8080, and runs as the nonroot (uid 65532) nginx user.

If you want to use the image with a shell and package manager, you can use the -dev variant of this image.

Getting Started

Elasticvue is a static Elasticsearch GUI that runs entirely in the browser. The container only serves the SPA assets — actual Elasticsearch traffic flows directly between the user's browser and your Elasticsearch cluster, so you must enable CORS on your Elasticsearch cluster.

Run with Docker

Run the container and expose port 8080:

docker run -p 8080:8080 --name elasticvue -d cgr.dev/ORGANIZATION/elasticvue:latest

Then open http://localhost:8080 in your browser and configure your Elasticsearch cluster from the UI.

Pre-configure clusters via environment variable

You can pre-load default clusters by passing a JSON array via the ELASTICVUE_CLUSTERS environment variable. The OCI entrypoint hook writes it to /usr/share/nginx/html/api/default_clusters.json on startup:

docker run -p 8080:8080 \
  -e ELASTICVUE_CLUSTERS='[{"name":"prod","uri":"http://localhost:9200","username":"elastic","password":"elastic"}]' \
  cgr.dev/ORGANIZATION/elasticvue:latest

Pre-configure clusters via mounted config file

Alternatively, mount a JSON file at /usr/share/nginx/html/api/default_clusters.json:

echo '[{"name":"prod","uri":"http://localhost:9200"}]' > config.json
docker run -p 8080:8080 \
  -v $(pwd)/config.json:/usr/share/nginx/html/api/default_clusters.json \
  cgr.dev/ORGANIZATION/elasticvue:latest

Deployment on Kubernetes

Elasticvue does not ship an official Helm chart. Deploy it with a standard Deployment + Service:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: elasticvue
spec:
  replicas: 1
  selector:
    matchLabels:
      app: elasticvue
  template:
    metadata:
      labels:
        app: elasticvue
    spec:
      containers:
        - name: elasticvue
          image: cgr.dev/ORGANIZATION/elasticvue:latest
          ports:
            - name: http
              containerPort: 8080
          env:
            - name: ELASTICVUE_CLUSTERS
              value: '[{"name":"prod","uri":"http://elasticsearch.default.svc.cluster.local:9200"}]'
---
apiVersion: v1
kind: Service
metadata:
  name: elasticvue
spec:
  selector:
    app: elasticvue
  ports:
    - name: http
      port: 8080
      targetPort: http

Apply and verify:

kubectl apply -f elasticvue.yaml
kubectl rollout status deployment/elasticvue
kubectl port-forward svc/elasticvue 8080:8080

Open http://localhost:8080 in your browser.

Documentation and Resources

• Project Repository
• Features
• FAQ
• Elasticsearch CORS configuration
• Default cluster configuration keys

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.