How to use this image

All examples in this guide use the public image. If you’ve mirrored the repository for your own use (for example, to your Docker Hub namespace), update your commands to reference the mirrored image instead of the public one.

For example:

• Public image: dhi.io/<repository>:<tag>
• Mirrored image: <your-namespace>/dhi-<repository>:<tag>

For the examples, you must first use docker login dhi.io to authenticate to the registry to pull the images.

Run Elasticsearch

First, create a user defined network. This will make it easier to connect to other services attached to the same network, like Kibana.

docker network create somenetwork

Run the following command to run an Elasticsearch container. Replace <tag> with the image variant you want to run.

docker run -d --name elasticsearch --net somenetwork -p 9200:9200 -p 9300:9300 -e "discovery.type=single-node" dhi.io/elasticsearch:<tag>

Next you need to reset the Elasticsearch password. Enter a bash shell for the container by running docker exec -it elasticsearch bash, then run the following command. If you get an error locating the path for the password reset tool, run find / -type f -name "elasticsearch-reset-password" 2>/dev/null to locate the full path and replace it in the command below.

/usr/share/elasticsearch/bin/elasticsearch-reset-password -u elastic -b

You should see a result like the following, note the newly generated password <YOUR-ELASTIC-PASSWORD>, you use it for the following example CURL calls.

Password for the [elastic] user successfully reset.
New value: <YOUR-ELASTIC-PASSWORD>

Common Elasticsearch use-cases

Check cluster health

curl -u elastic:<YOUR-ELASTIC-PASSWORD> -k "https://localhost:9200/_cluster/health?pretty"

Create an index

curl -u elastic:<YOUR-ELASTIC-PASSWORD> -k -X PUT "https://localhost:9200/my-index?pretty"

Index a document

curl -u elastic:<YOUR-ELASTIC-PASSWORD> -k -X POST "https://localhost:9200/my-index/_doc/1?pretty" \
  -H 'Content-Type: application/json' \
  -d '{
    "title": "Elasticsearch Basics",
    "tags": ["docker", "search"],
    "published": "2025-09-30"
  }'

Retrieve a document

curl -u elastic:<YOUR-ELASTIC-PASSWORD> -k -X GET "https://localhost:9200/my-index/_doc/1?pretty"

Search documents

curl -u elastic:<YOUR-ELASTIC-PASSWORD> -k -X GET "https://localhost:9200/my-index/_search?pretty" \
  -H 'Content-Type: application/json' \
  -d '{
    "query": {
      "match": { "title": "Elasticsearch" }
    }
  }'

List all indices

curl -u elastic:<YOUR-ELASTIC-PASSWORD> -k "https://localhost:9200/_cat/indices?v"

Delete an index

curl -u elastic:<YOUR-ELASTIC-PASSWORD> -k -X DELETE "https://localhost:9200/my-index?pretty"

Docker Compose example

To use Elasticsearch in a multi-service environment, create the following docker-compose.yml. This example adds Kibana to the environment, note that <YOUR-ELASTIC-PASSWORD> is included in the Kibana config.

version: '3'
services:
  elasticsearch:
    image: dhi.io/elasticsearch:<tag>
    environment:
      - node.name=es01
      - discovery.type=single-node
    ports:
      - "9200:9200"

  kibana:
    image: dhi.io/kibana:<tag>
    ports:
      - "5601:5601"
    environment:
      - ELASTICSEARCH_HOSTS=http://elasticsearch:9200
      - ELASTICSEARCH_USERNAME=elastic
      - ELASTICSEARCH_PASSWORD=<YOUR-ELASTIC-PASSWORD>
      # Skip certificate verification if using self-signed cert
      - ELASTICSEARCH_SSL_VERIFICATIONMODE=none

Run the environment by running docker compose up -d in the same directory.

Deploy with Elastic Cloud on Kubernetes (ECK)

You can deploy the Debian 13 Elasticsearch image with Elastic Cloud on Kubernetes (ECK)⁠. Use a current Debian 13 image tag, such as dhi.io/elasticsearch:8.19.1-debian13, so the ECK readiness probe can find nc in the standard container PATH.

For ECK, set a numeric pod security context so Kubernetes can verify the container runs as a non-root user:

apiVersion: elasticsearch.k8s.elastic.co/v1
kind: Elasticsearch
metadata:
  name: elasticsearch-sample
spec:
  version: 8.19.1
  image: dhi.io/elasticsearch:8.19.1-debian13
  nodeSets:
    - name: default
      count: 1
      config:
        node.store.allow_mmap: false
      podTemplate:
        spec:
          securityContext:
            runAsUser: 1000
            fsGroup: 1000

Replace the version and image tag with the Elasticsearch release you want to run. Keep the values aligned so ECK and the container image use the same Elasticsearch version.

After you apply the manifest, verify the workload with:

kubectl get elasticsearch
kubectl get pods
kubectl describe pod <pod-name>
kubectl logs <pod-name>

Troubleshooting ECK deployments

• If Kubernetes reports runAsNonRoot errors, set runAsUser: 1000 and fsGroup: 1000 in the ECK podTemplate security context.
• If the readiness probe fails, confirm you are using a current Debian 13 image tag and check that nc is available in the standard path:

kubectl exec -it <pod-name> -- env -i PATH=/usr/bin:/bin:/usr/sbin:/sbin bash -c 'which nc'

• ECK uses its own readiness probe script. If the pod is running but not ready, inspect the probe failure with kubectl describe pod <pod-name> and compare it with the ECK readiness probe documentation⁠.

Image variants

Docker Hardened Images come in different variants depending on their intended use.

• Runtime variants are designed to run your application in production. These images are intended to be used either directly or as the FROM image in the final stage of a multi-stage build. These images typically:

  • Run as the nonroot user
  • Do not include a shell or a package manager
  • Contain only the minimal set of libraries needed to run the app

• Build-time variants typically include dev in the variant name and are intended for use in the first stage of a multi-stage Dockerfile. These images typically:

  • Run as the root user
  • Include a shell and package manager
  • Are used to build or compile applications

• FIPS variants include fips in the variant name and tag. They come in both runtime and build-time variants. These variants use cryptographic modules that have been validated under FIPS 140, a U.S. government standard for secure cryptographic operations. For example, usage of MD5 fails in FIPS variants.

Migrate to a Docker Hardened Image

To migrate your application to a Docker Hardened Image, you must update your Dockerfile. At minimum, you must update the base image in your existing Dockerfile to a Docker Hardened Image. This and a few other common changes are listed in the following table of migration notes.

The following steps outline the general migration process.

1. Find hardened images for your app.

   A hardened image may have several variants. Inspect the image tags and find the image variant that meets your needs.

2. Update the base image in your Dockerfile.

   Update the base image in your application's Dockerfile to the hardened image you found in the previous step. For framework images, this is typically going to be an image tagged as dev because it has the tools needed to install packages and dependencies.

3. For multi-stage Dockerfiles, update the runtime image in your Dockerfile.

   To ensure that your final image is as minimal as possible, you should use a multi-stage build. All stages in your Dockerfile should use a hardened image. While intermediary stages will typically use images tagged as dev, your final runtime stage should use a non-dev image variant.

4. Install additional packages

   Docker Hardened Images contain minimal packages in order to reduce the potential attack surface. You may need to install additional packages in your Dockerfile. Inspect the image variants to identify which packages are already installed.

   Only images tagged as dev typically have package managers. You should use a multi-stage Dockerfile to install the packages. Install the packages in the build stage that uses a dev image. Then, if needed, copy any necessary artifacts to the runtime stage that uses a non-dev image.

   For Alpine-based images, you can use apk to install packages. For Debian-based images, you can use apt-get to install packages.

Troubleshooting migration

The following are common issues that you may encounter during migration.

General debugging

The hardened images intended for runtime don't contain a shell nor any tools for debugging. The recommended method for debugging applications built with Docker Hardened Images is to use Docker Debug⁠ to attach to these containers. Docker Debug provides a shell, common debugging tools, and lets you install other tools in an ephemeral, writable layer that only exists during the debugging session.

Permissions

By default image variants intended for runtime, run as the nonroot user. Ensure that necessary files and directories are accessible to the nonroot user. You may need to copy files to different directories or change permissions so your application running as the nonroot user can access them.

Privileged ports

Non-dev hardened images run as a nonroot user by default. As a result, applications in these images can't bind to privileged ports (below 1024) when running in Kubernetes or in Docker Engine versions older than 20.10. To avoid issues, configure your application to listen on port 1025 or higher inside the container, even if you map it to a lower port on the host. For example, docker run -p 80:8080 my-image will work because the port inside the container is 8080, and docker run -p 80:81 my-image won't work because the port inside the container is 81.

No shell

By default, image variants intended for runtime don't contain a shell. Use dev images in build stages to run shell commands and then copy any necessary artifacts into the runtime stage. In addition, use Docker Debug to debug containers with no shell.

Entry point

Docker Hardened Images may have different entry points than images such as Docker Official Images. Use docker inspect to inspect entry points for Docker Hardened Images and update your Dockerfile if necessary.