How to create Elasticsearch docker container, create indexes and seed data in one step?

rpm1984 · February 8, 2019, 1:55am

Hi there!

So i'm using the Elasticsearch docker image to develop locally. Works great.

Now what i'd like to do as part of a docker-compose script is to:

Create an instance of Elasticsearch via docker image
Create index
Import data using Bulk API (e.g a JSON file in the source control repository)

Initially i was thinking i could have a Dockerfile that started from the Elasticsearch base image, then somehow used curl commands to index/add data, but the issue is the container isn't 'up' yet.

The ideal situation is i'd like to run a command like this:

docker-compose up my-elastic-search-db

Then everything is up and ready to go.

How do people solve this? I've seen a few posts that a few years old of people running scripts 'waiting' for it to be up.. so just seeing if this is still the way, or have Elastic made it easier.

dadoonet · February 8, 2019, 3:17am

May be have a look at the healthcheck part of this example:

github.com

elastic/stack-docker/blob/master/docker-compose.yml

---
version: '3.6'
services:
  # The environment variable "TAG" is used throughout this file to
  # specify the version of the images to run. The default is set in the
  # '.env' file in this folder. It can be overridden with any normal
  # technique for setting environment variables, for example:
  #
  #   TAG=6.0.0-beta1 docker-compose up
  #
  # REF: https://docs.docker.com/compose/compose-file/#variable-substitution
  #
  # Also be sure to set the ELASTIC_VERSION variable. For released versions,
  # ${TAG} and ${ELASTIC_VERSION} will be identical, but for pre-release
  # versions, ${TAG} might contain an extra build identifier, like
  # "6.0.0-beta1-3eab5b40", so a full invocation might look like:
  #
  #   ELASTIC_VERSION=6.0.0-beta1 TAG=6.0.0-beta1-3eab5b40 docker-compose up
  #
  elasticsearch:

This file has been truncated. show original

rpm1984 · February 8, 2019, 5:07am

Hi @dadoonet, thanks for the answer.

Can you please elaborate on how healthcheck can help?

When and where would my 'curl' occur to insert the data? It can't be in the custom Dockerfile for the elasticsearch image right? It would need to be after the healthcheck..

So.. would i just have another 'service' in docker compose that depends_on the elasticsearch image, and this 'service' is actually just a script that uses curl to insert the data?

dadoonet · February 8, 2019, 10:39am

Yes. That's my feeling too.

system · March 8, 2019, 10:39am

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.