This repository is a clone from pires/docker-elasticsearch:2.4.1 but with a different base image which trying to fix the startup issue as mentioned in Seldom exceptions with Alpine and multiple container layers.
In order to replace the alpine base image, AtzeDeVries/kubernetes-elasticsearch is also referenced.
Very lean (140MB) and highly configurable Elasticsearch Docker image.
- OpenJDK 8u92
- Elasticsearch 2.4.1
- In order for
bootstrap.mlockall
to work,ulimit
must be allowed to run in the container. Run with--privileged
to enable this. - Multicast discovery is no longer built-in
Ready to use node for cluster elasticsearch-default
:
docker run --name elasticsearch \
--detach \
--privileged \
--volume /path/to/data_folder:/data \
quay.io/pires/docker-elasticsearch:2.4.1
Ready to use node for cluster myclustername
:
docker run --name elasticsearch \
--detach \
--privileged \
--volume /path/to/data_folder:/data \
-e CLUSTER_NAME=myclustername \
quay.io/pires/docker-elasticsearch:2.4.1
Ready to use node for cluster elasticsearch-default
, with 8GB heap allocated to Elasticsearch:
docker run --name elasticsearch \
--detach \
--privileged \
--volume /path/to/data_folder:/data \
-e ES_HEAP_SIZE=8G \
quay.io/pires/docker-elasticsearch:2.4.1
Master-only node for cluster elasticsearch-default
:
docker run --name elasticsearch \
--detach \
--privileged \
--volume /path/to/data_folder:/data \
-e NODE_DATA=false \
-e HTTP_ENABLE=false \
quay.io/pires/docker-elasticsearch:2.4.1
Data-only node for cluster elasticsearch-default
:
docker run --name elasticsearch \
--detach --volume /path/to/data_folder:/data \
--privileged \
-e NODE_MASTER=false \
-e HTTP_ENABLE=false \
quay.io/pires/docker-elasticsearch:2.4.1
Client-only node for cluster elasticsearch-default
:
docker run --name elasticsearch \
--detach \
--privileged \
--volume /path/to/data_folder:/data \
-e NODE_MASTER=false \
-e NODE_DATA=false \
quay.io/pires/docker-elasticsearch:2.4.1
I also make available special images and instructions for AWS EC2 and Kubernetes.
This image can be configured by means of environment variables, that one can set on a Deployment
.