Self-host Elasticsearch + Kibana with Levelrail

Elasticsearch paired with Kibana for log and document search with a visual dashboard. Kibana has no login, so anyone who can open it controls the data: before attaching a domain, enable Basic Auth or the auth gate on it. Elasticsearch is reachable only from services in this project at elasticsearch:9200 and is not published on the host.

  • Memory2 GiB
  • Archarm64
  • Services2

How to self-host Elasticsearch + Kibana

  1. Pull the images

    2 images are pulled on your server.

    Show images
    • elasticsearch:9.1.2
    • kibana:9.1.2
  2. Create the app

    2 services start in a single Compose app, with 1 named volume mount for your data, on ports 9200, 5601.

  3. Fill in the secrets

    1 secret is generated and stored encrypted, 5 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 + Kibana requirements

Memory
About 2 GiB
Architectures
amd64 image published, arm64 image published
Ports
9200, 5601
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 + Kibana. 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 + Kibana docs page.

Deploy Elasticsearch + Kibana your way

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

Deploy Elasticsearch + Kibana from the CLI

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

Deploy Elasticsearch + Kibana 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-kibana/deploy

Elasticsearch + Kibana configuration

Elasticsearch + Kibana services

ServiceImagePortsVolumes
elasticsearch elasticsearch:9.1.2 9200 es_data -> /usr/share/elasticsearch/data
kibana kibana:9.1.2 5601 none

Elasticsearch + Kibana 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
ELASTICSEARCH_HOSTS kibana Preset by the template
SERVER_PUBLICBASEURL kibana Preset by the template
XPACK_ENCRYPTEDSAVEDOBJECTS_ENCRYPTIONKEY kibana Generated at deploy

Ports and volumes

Ports
9200, 5601
Volumes
1 named mount: es_data -> /usr/share/elasticsearch/data

Elasticsearch + Kibana FAQ

How much memory does Elasticsearch + Kibana need?

The catalog lists about 2 GiB of memory for Elasticsearch + Kibana across its 2 services.

Does Elasticsearch + Kibana run on arm64?

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

Does Elasticsearch + Kibana need configuration before it starts?

No. The template fills in its own defaults and generates secrets at deploy time.

Which database does Elasticsearch + Kibana bundle?

The template includes Elasticsearch, running as its own service.

Which ports does Elasticsearch + Kibana use?

Elasticsearch + Kibana listens on ports 9200 and 5601 inside the stack.

Where does Elasticsearch + Kibana keep its data?

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

Can I deploy Elasticsearch + Kibana on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Elasticsearch + Kibana, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image elasticsearch:9.1.2, kibana:9.1.2 is what you deploy there.

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