• Last Updated: 30 Sep 2023
• Category
• Arvind Das

Elasticsearch minimal configuration for docker compose single node

Hi Everyone,

Today we are going to look at the minimal configuration required to run Elasticsearch. The search service from Elastic is still free . You can use it without a hitch.

Elasticsearch is one of the leading search engine servers and the ease of integration using the REST integration makes it developer friendly and first choice.

In our today's blog we will see how to spin up an Elasticsearch docker container using docker compose.

Docker compose is preferable choice for developers simply because it provides easy of configuring their container and runtime configuration which becomes tedious on command line when you have too many settings/environment variables.

So lets look at it

version: '3'
services:
  elasticsearch:
    container_name: es01
    image: docker.elastic.co/elasticsearch/elasticsearch:8.10.2
    ports:
      - 9200:9200
    networks:
      - elastic
    volumes:
      - ./esdata:/usr/share/elasticsearch/data
    environment:
      - discovery.type=single-node
      - ELASTIC_PASSWORD=admin
      - ELASTIC_USERNAME=admin    
    deploy:
      resources:
          limits:
            cpus: '2.0'
            memory: 1G  
          reservations:
            cpus: '1.0'
            memory: 1G  
volumes:
  esdata:              
networks:
  elastic:

So, if you look at it this has

1. Minimal configuration, no Kibana setup required , you could simply use curl commands to create your indexes and you are good to go.
2. We configured volumes just to retain the data next time we spin up the container.
3. CPU and Memory limits are set to a minimal, if we do not set them, this is going to consume a lot of these resources .

Hope it helps.

Thanks!