Portainer Templates logo

Portainer Templates

Elasticsearch Elasticsearch

Container

Database

Open-source search and analytics engine

Configuration

Type
Container
Platform
linux
Image
docker.elastic.co/elasticsearch/elasticsearch:7.15.1
Ports
9200/tcp9300/tcp
Volumes
/usr/share/elasticsearch/data

Template by portainer

Standalone Install

Select an install method, to see config/commands for deploying Elasticsearch

Installation method

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select Elasticsearch, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo

More install options in our documentation.

Serve Elasticsearch on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.

Proxying elasticsearch.example.com to http://elasticsearch:9200

Add this to your Caddyfile

elasticsearch.example.com {
	reverse_proxy http://elasticsearch:9200
}

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs <container>
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Published on a random port

This template exposes 9200/tcp without setting a host port, so Docker picks a random free one on every deploy.

  • Find it in the Ports column of Portainer's container list, or with docker port <container>

Image won't pull

Test the pull directly on the host: docker pull docker.elastic.co/elasticsearch/elasticsearch:7.15.1

  • "manifest unknown" means the tag no longer exists.
  • "toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
  • "no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

A single container

Elasticsearch runs as one container, the simplest kind of app here. Just the one image to pull and nothing else wired up alongside it.

The app image

An image is the app packed up ready to go, everything Elasticsearch needs bundled into one download. This template pulls docker.elastic.co/elasticsearch/elasticsearch:7.15.1, which Docker fetches once and then starts your own copy from.

Where the image comes from

Docker pulls its images from registries, public libraries of ready-built apps. Elasticsearch's comes from docker.elastic.co, published by elasticsearch.

Version tags

The bit after the colon in the image name is the version tag. This one pins 7.15.1, so every redeploy gives you that exact build until you bump it yourself.

Ports

A port is the door the app answers on. Here the app exposes a port but leaves the host side blank, so Docker picks a free one for you. It opens:

  • 9200, published on a random host port
  • 9300, published on a random host port

Volumes

A volume is where Elasticsearch keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:

  • /usr/share/elasticsearch/data as a volume Docker manages for you

Networking

Nothing custom is set, so Elasticsearch sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.

Platform

The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Elasticsearch up. Add the template list to Portainer once, then deploying Elasticsearch is a click rather than a wall of config.