Self-host Elasticsearch with Levelrail

A distributed, RESTful search and analytics engine for full-text search and log analytics. Security is off, so reach it from other services in this project at elasticsearch:9200, or attach a domain only behind Basic Auth. Not published on the host.

  • Memory1 GiB
  • Archarm64
  • Services1

How to self-host Elasticsearch

  1. Pull the images

    One image is pulled on your server.

    Show images
    • docker.elastic.co/elasticsearch/elasticsearch:8.19.22
  2. Create the app

    One service starts in a single Compose app, with 1 named volume mount for your data, on port 9200.

  3. Fill in the secrets

    3 settings are preset, you do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

Elasticsearch requirements

Memory
About 1 GiB
Architectures
amd64 image published, arm64 image published
Ports
9200
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
not yet recorded
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Elasticsearch. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the Elasticsearch docs page.

Deploy Elasticsearch your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy Elasticsearch from the CLI

levelrail-cli templates deploy elasticsearch --name my-elasticsearch

Deploy Elasticsearch with the API

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/elasticsearch/deploy

Elasticsearch configuration

Elasticsearch services

ServiceImagePortsVolumes
elasticsearch docker.elastic.co/elasticsearch/elasticsearch:8.19.22 9200 elasticsearch_data -> /usr/share/elasticsearch/data

Elasticsearch environment variables

VariableServiceValue
ES_JAVA_OPTS elasticsearch Preset by the template
discovery.type elasticsearch Preset by the template
xpack.security.enabled elasticsearch Preset by the template

Ports and volumes

Ports
9200
Volumes
1 named mount: elasticsearch_data -> /usr/share/elasticsearch/data

Elasticsearch FAQ

How much memory does Elasticsearch need?

The catalog lists about 1 GiB of memory for Elasticsearch.

Does Elasticsearch run on arm64?

For Elasticsearch, an arm64 image is published; amd64 is image published.

Does Elasticsearch need configuration before it starts?

No. The template fills in its own defaults.

Which database does Elasticsearch bundle?

The template includes Elasticsearch, running as part of the stack.

Which ports does Elasticsearch use?

Elasticsearch listens on port 9200 inside the stack.

Where does Elasticsearch keep its data?

In a named volume: elasticsearch_data mounted at /usr/share/elasticsearch/data.

Can I deploy Elasticsearch on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id elastic-search for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image docker.elastic.co/elasticsearch/elasticsearch:8.19.22 is what you deploy there.

levelrail-cli templates deploy elasticsearch --name my-elasticsearch