Run Elasticsearch image on Azure Container Instances

Last week I was moving a Docker application to Azure Container Instances. The application consisted out of 3 containers and one of them was using the official image of Elasticsearch:

FROM docker.elastic.co/elasticsearch/elasticsearch:5.3.0 

Unlucky the container was failing to start, giving the following error:

max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144] 

After a quick search, I found this post where someone else was having the same problem.

I did some attempts to give more memory and CPU to the container, but it didn’t solve the problem because it needs changes at the host.

Azure Container Instances (ACI) is a serverless docker hosting environment (not an orchestrator!), I call it Pod as a Service, there’s no way to change or tweak things at host level.

Solution

On the Docker Hub there are other elasticsearch images available, and finally I got it working on ACI using:

FROM elasticsearch:5.6.14-alpine

One thought on “Run Elasticsearch image on Azure Container Instances

Add yours

  1. Thanks, but running an old version of Elasticsearch is not an answer anymore. Do you have new info about this? How can we run Elasticsearch container in Azure as of June 2019?

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Blog at WordPress.com.

Up ↑

%d bloggers like this: