// Bitnami alternatives / elasticsearch

Bitnami Elasticsearch alternative
Replacing bitnamilegacy/elasticsearch

The bitnamilegacy/elasticsearch image has had about 1.4 million pulls since Bitnami moved it to the legacy repository, and it receives no updates. Switching to the official elasticsearch (docker.elastic.co/elasticsearch/elasticsearch) image means changing environment variables and the data path. Get either wrong and the new container starts empty.

Get a drop-in Elasticsearch image

Trusted globally by enterprises

Henry ScheinEnbridgeGojekMicrosoft

Bitnami Elasticsearch variables and their official equivalents

Bitnami Elasticsearch image to official elasticsearch (docker.elastic.co/elasticsearch/elasticsearch):

SettingBitnamiOfficial image
Cluster nameELASTICSEARCH_CLUSTER_NAMEcluster.name
Discovery hostsELASTICSEARCH_CLUSTER_HOSTSdiscovery.seed_hosts
Single node in developmentDefault configurationdiscovery.type=single-node
Data path/bitnami/elasticsearch/data/usr/share/elasticsearch/data

What breaks when you switch

  • The official image reads Elasticsearch settings directly as environment variables named after the setting, such as discovery.type.
  • Official 8.x images enable security by default, and cannot start with indices created before 7.0.
  • Newer Elasticsearch releases are not Apache-2.0 licensed. OpenSearch is the Apache-2.0 alternative.

What happened to the Bitnami Elasticsearch image

For years, bitnami/elasticsearch on Docker Hub was one of the most common ways to deploy Elasticsearch on Kubernetes, usually through the Bitnami Elasticsearch Helm chart. On 28 August 2025 Broadcom moved every versioned Bitnami container image, including this one, to the bitnamilegacy repository, and removed the public docker.io/bitnami catalog on 29 September 2025. The free tier now offers only latest tags of a limited set of images for development.

The legacy Docker image still pulls, so existing deployments keep working. It no longer receives updates, which means every vulnerability disclosed since the move stays open in the Elasticsearch binary, in the base image and in every bundled dependency. Container scanners will report a growing count at every audit, and a workload that depends on a frozen public repository is one registry change away from ImagePullBackOff.

How to migrate Elasticsearch off Bitnami safely

  1. Find every reference to bitnami/elasticsearch and bitnamilegacy/elasticsearch in running workloads, Helm values files and CI pipelines, including init containers.
  2. Record the Elasticsearch version each deployment pins. Versions past upstream end of life are not covered by the free open source images.
  3. Take a backup and test a restore before touching a stateful workload.
  4. Mirror the replacement container images into your own registry, and scan them before you deploy.
  5. Move one replica or one environment at a time, and confirm the data path, file ownership and credentials on the new image.
  6. Remove every remaining legacy reference so nothing falls back to the archive on the next deploy.

Your options

OSSeva drop-in image

A patched image that keeps Bitnami's variables, paths and user, covering Elasticsearch 7.10.2 and 7.17. Your chart keeps working after a registry change.

Official elasticsearch (docker.elastic.co/elasticsearch/elasticsearch) image

Free and maintained for current versions. Apply the mapping above and move the volume.

Bitnami Secure Images

Broadcom's paid catalog keeps the Bitnami layout for supported versions, sold within TrueSource.

Repoint the Bitnami Elasticsearch Helm chart

# values-override.yaml
image:
  registry: registry.example.com   # your mirror of the replacement image
  repository: elasticsearch
  tag: "<pinned version>"
global:
  security:
    allowInsecureImages: true      # recent Bitnami charts reject non-Bitnami images without this

This works only with an image that keeps Bitnami's layout. With the official image, rewrite the chart or move to an operator. See replacing bitnamilegacy images for the full inventory and rollout steps.

Frequently asked questions

What is the best alternative to the Bitnami Elasticsearch image?

To keep the Bitnami Elasticsearch Helm chart unchanged, use a Bitnami-compatible image; OSSeva ships patched ones covering Elasticsearch 7.10.2 and 7.17. To rewrite the deployment, use the official elasticsearch (docker.elastic.co/elasticsearch/elasticsearch) image.

Is bitnamilegacy/elasticsearch still getting security updates?

No. Bitnami moved versioned images to the bitnamilegacy repository on 28 August 2025 and describes it as receiving no further updates. It had about 1.4 million pulls by September 2026.

Can I keep using the Bitnami Elasticsearch Helm chart?

Yes, with a maintained image that keeps Bitnami's layout. Set image.registry and image.repository in your values file, and set global.security.allowInsecureImages to true, because recent Bitnami charts refuse non-Bitnami images otherwise.

Is Bitnami no longer free?

Not for production. Since 28 August 2025, versioned Bitnami images live in the bitnamilegacy repository with no updates, and the free tier offers latest tags of a limited set of images for development. Maintained, versioned images are sold as Bitnami Secure Images, which Broadcom prices by quote.

Where does the Bitnami Elasticsearch image store data?

Under /bitnami/elasticsearch/data. The official image uses /usr/share/elasticsearch/data, so the volume mount must change when you switch images.

Keep your Elasticsearch chart. Change the image.

Send us your image list and versions; we reply with coverage and a migration plan within five working days.

Book a Discovery CallAll Bitnami alternatives →