
khezen/elasticsearchElasticsearch is a distributed, RESTful search and analytics engine capable of solving a growing number of use cases. As the heart of the Elastic Stack, it centrally stores your data so you can discover the expected and uncover the unexpected. This image uses search-guard instead of shield to handle trusted users.
[]([***]
docker run -d -p 9200:9200 -p 9300:9300 -e ELASTIC_PWD=changeme -e KIBANA_PWD=changeme khezen/elasticsearch:latest
version: '2' services: elasticsearch: image: khezen/elasticsearch:5 environment: ELASTIC_PWD: changeme KIBANA_PWD: changeme volumes: - /data/elasticsearch:/usr/share/elasticsearch/data - /etc/elasticsearch:/usr/share/elasticsearch/config ports: - "9200:9200" - "9300:9300" network_mode: bridge restart: always
run the following command on your host:
sysctl -w vm.max_map_count=262144
You can set it permanently by modifying vm.max_map_count setting in your /etc/sysctl.conf.
LOG_LEVEL | INFO
Log level from witch elasticsearch echoes logs.
CLUSTER_NAME | elasticsearch
ES cluster name.
MINIMUM_MASTER_NODES | 1
This setting) tells Elasticsearch to not elect a master unless there are enough master-eligible nodes available. Only then will an election take place.
We recommand to set this variable to (number of nodes / 2) + 1
HOSTS | 127.0.0.1, [::1]
List of hosts for node discovery (discovery.zen.ping.unicast.hosts)
NODE_NAME | NODE-1
ES cluster name.
NODE_MASTER | true
Set to true (default) makes it eligible to be elected as the master node, which controls the cluster.
NODE_DATA | true
Data nodes hold data and perform data related operations such as CRUD, search, and aggregations.
NODE_INGEST | true
Ingest nodes are able to apply an ingest pipeline to a document in order to transform and enrich the document before indexing. With a heavy ingest load, it makes sense to use dedicated ingest nodes and to mark the master and data nodes as NODE_INGEST: false
.
HTTP_ENABLE | true
http can be completely disabled and not started by setting HTTP_ENABLE to false. Elasticsearch nodes (and Java clients) communicate internally using the transport interface, not HTTP. It might make sense to disable the http layer entirely on nodes which are not meant to serve REST requests directly. For instance, you could disable HTTP on data-only nodes if you also have client nodes which are intended to serve all REST requests. Be aware, however, that you will not be able to send any REST requests (eg to retrieve node stats) directly to nodes which have HTTP disabled.
HTTP_CORS_ENABLE | true
Enable or disable cross-origin resource sharing, i.e. whether a browser on another origin can execute requests against Elasticsearch. Note that if the client does not send a pre-flight request with an Origin header or it does not check the response headers from the server to validate the Access-Control-Allow-Origin response header, then cross-origin security is compromised.
HTTP_CORS_ALLOW_ORIGIN | *
Which origins to allow. Note that * is a valid value but is ***ed a security risk as your elasticsearch instance is open to cross origin requests from anywhere.
NETWORK_HOST |0.0.0.0
The node will bind to this hostname or IP address and advertise this host to other nodes in the cluster. Accepts an IP address, hostname, a special value, or an array of any combination of these.
HEAP_SIZE | 1g
Defines the memory available to the JVM.
ELASTIC_PWD | changeme
password for built-in user elastic.
KIBANA_PWD | changeme
password for built-in user kibana.
LOGSTASH_PWD | changeme
password for built-in user logstash.
BEATS_PWD | changeme
password for built-in user beats.
CA_PWD | changeme
CA certificate passphrase.
TS_PWD | changeme
Truststore(public keys storage) password.
KS_PWD | changeme
Keystore(private key storage) password.
HTTP_SSL | true
Configuration file is located in /etc/elasticsearch/elasticsearch.yml if you follow the same volume mapping as in the docker-compose example above.
You can find default config there.
You can find help with elasticsearch configuration there.
If you have any problems with or questions about this image, please ask for help through a GitHub issue.



manifest unknown 错误
TLS 证书验证失败
DNS 解析超时
410 错误:版本过低
402 错误:流量耗尽
身份认证失败错误
429 限流错误
凭证保存错误
来自真实用户的反馈,见证轩辕镜像的优质服务