Commit d05f0752 by yinyong

'update'

parent a078f3d5
FROM docker.elastic.co/elasticsearch/elasticsearch:5.6.10
LABEL maintainer="jian.tan@daocloud.io"
USER root
RUN ln -sf /usr/share/zoneinfo/Asia/Shanghai /etc/localtime \
&& echo "Asia/Shanghai" > /etc/timezone \
&& chown elasticsearch:elasticsearch config/elasticsearch.yml
USER elasticsearch
# elasticsearch-Zone-Asia-SH
[![Docker Build Status](https://img.shields.io/docker/build/wutang/skywalking-docker.svg)](https://hub.docker.com/r/wutang/skywalking-docker/)
[![Docker Pulls](https://img.shields.io/docker/pulls/wutang/elasticsearch-shanghai-zone.svg)](https://hub.docker.com/r/wutang/elasticsearch-shanghai-zone/)
[![Docker Automated build](https://img.shields.io/docker/automated/wutang/elasticsearch-shanghai-zone.svg)](https://hub.docker.com/r/wutang/elasticsearch-shanghai-zone/builds/)
[![ImageLayers Size](https://img.shields.io/imagelayers/image-size/wutang/elasticsearch-shanghai-zone/latest.svg)](https://hub.docker.com/r/wutang/elasticsearch-shanghai-zone/)
[![ImageLayers Layers](https://img.shields.io/imagelayers/layers/wutang/elasticsearch-shanghai-zone/latest.svg)](https://hub.docker.com/r/wutang/elasticsearch-shanghai-zone/)
Docker 镜像名称:[wutang/elasticsearch-shanghai-zone:5.6.10](https://hub.docker.com/r/wutang/elasticsearch-shanghai-zone/)
此镜像主要对官方的Elasticsearch的```docker.elastic.co/elasticsearch/elasticsearch:5.6.10```镜像做了封装,调整了镜像时区(Asia/ShangHai),解决了在运行Skywalking的时候连接Elasticsearch时报错的问题。
## 拉取镜像(Pull Image):
```docker pull wutang/elasticsearch-shanghai-zone:5.6.10```
## 运行镜像(Run):
```docker run -p 9200:9200 -p 9300:9300 -e cluster.name=elasticsearch -e xpack.security.enabled=false -d wutang/elasticsearch-shanghai-zone:5.6.10```
## 环境变量(Environment Variables)
```cluster.name```
Elasticsearch集群名称,运行Skywalking需要与此名称保持一致。
```xpack.security.enabled```
是否开启xpack安全验证,在运行Skywalking中需要将其关闭。
## 与Skywalking-Docker镜像配合使用请参考
- [wutang/skywalking-docker](https://hub.docker.com/r/wutang/skywalking-docker/)镜像[使用说明](../5.x/standalone/all-in-one/README.md)
- [quick start](../5.x/quick-start/README.md)
FROM docker.elastic.co/elasticsearch/elasticsearch:6.3.2
LABEL maintainer="jian.tan@daocloud.io"
ENV discovery.type=single-node \
xpack.security.enabled=false \
cluster.name=elasticsearch \
bootstrap.memory_lock=true
USER root
COPY /elasticsearch-Zone-Asia-SH/6.3.2/elasticsearch.yml /config/elasticsearch.yml
RUN ln -sf /usr/share/zoneinfo/Asia/Shanghai /etc/localtime \
&& echo "Asia/Shanghai" > /etc/timezone \
&& chown elasticsearch:elasticsearch config/elasticsearch.yml
USER elasticsearch
# elasticsearch-Zone-Asia-SH
Docker 镜像名称:[wutang/elasticsearch-shanghai-zone](https://hub.docker.com/r/wutang/elasticsearch-shanghai-zone/)
此镜像主要对官方的Elasticsearch的```docker.elastic.co/elasticsearch/elasticsearch:6.3.2```镜像做了封装,调整了镜像时区(Asia/ShangHai),解决了在运行Skywalking的时候连接Elasticsearch时报错的问题。
## 拉取镜像(Pull Image):
```docker pull wutang/elasticsearch-shanghai-zone:6.3.2```
## 运行镜像(Run):
```docker run -p 9200:9200 -p 9300:9300 -e cluster.name=elasticsearch -d wutang/elasticsearch-shanghai-zone:6.3.2```
## 环境变量(Environment Variables)
```cluster.name```
Elasticsearch集群名称,运行Skywalking需要与此名称保持一致。
cluster.name: "docker-cluster"
network.host: 0.0.0.0
# minimum_master_nodes need to be explicitly set when bound on a public IP
# set to 1 to allow single node clusters
# Details: https://github.com/elastic/elasticsearch/pull/17288
discovery.zen.minimum_master_nodes: 1
FROM docker.elastic.co/elasticsearch/elasticsearch:6.6.2
LABEL maintainer="jian.tan@daocloud.io"
ENV discovery.type=single-node \
xpack.security.enabled=false \
cluster.name=CollectorDBCluster \
bootstrap.memory_lock=true
USER root
COPY /elasticsearch-Zone-Asia-SH/6.6.2/elasticsearch.yml /config/elasticsearch.yml
RUN ln -sf /usr/share/zoneinfo/Asia/Shanghai /etc/localtime \
&& echo "Asia/Shanghai" > /etc/timezone \
&& chown elasticsearch:elasticsearch config/elasticsearch.yml
USER elasticsearch
# elasticsearch-Zone-Asia-SH
Docker 镜像名称:[wutang/elasticsearch-shanghai-zone](https://hub.docker.com/r/wutang/elasticsearch-shanghai-zone/)
此镜像主要对官方的Elasticsearch的```docker.elastic.co/elasticsearch/elasticsearch:6.6.2```镜像做了封装,调整了镜像时区(Asia/ShangHai),解决了在运行Skywalking的时候连接Elasticsearch时报错的问题。
## 拉取镜像(Pull Image):
```docker pull wutang/elasticsearch-shanghai-zone:6.6.2```
## 运行镜像(Run):
```docker run -p 9200:9200 -p 9300:9300 -e cluster.name=elasticsearch -d wutang/elasticsearch-shanghai-zone:6.6.2```
## 环境变量(Environment Variables)
```cluster.name```
Elasticsearch集群名称,运行Skywalking需要与此名称保持一致。
cluster.name: "CollectorDBCluster"
network.host: 0.0.0.0
# minimum_master_nodes need to be explicitly set when bound on a public IP
# set to 1 to allow single node clusters
# Details: https://github.com/elastic/elasticsearch/pull/17288
discovery.zen.minimum_master_nodes: 1
FROM elasticsearch:7.0.1
LABEL maintainer="jian.tan@daocloud.io"
ENV discovery.type=single-node \
xpack.security.enabled=false \
cluster.name=elasticsearch \
bootstrap.memory_lock=true
USER root
COPY elasticsearch.yml /config/elasticsearch.yml
RUN ln -sf /usr/share/zoneinfo/Asia/Shanghai /etc/localtime \
&& echo "Asia/Shanghai" > /etc/timezone \
&& chown elasticsearch:elasticsearch config/elasticsearch.yml
USER elasticsearch
# elasticsearch-Zone-Asia-SH
Docker 镜像名称:[wutang/elasticsearch-shanghai-zone](https://hub.docker.com/r/wutang/elasticsearch-shanghai-zone/)
此镜像主要对官方的Elasticsearch的```docker.elastic.co/elasticsearch/elasticsearch:7.0.1```镜像做了封装,调整了镜像时区(Asia/ShangHai),解决了在运行Skywalking的时候连接Elasticsearch时报错的问题。
## 拉取镜像(Pull Image):
```docker pull wutang/elasticsearch-shanghai-zone:7.0.1```
## 运行镜像(Run):
```docker run -p 9200:9200 -p 9300:9300 -e cluster.name=elasticsearch -d wutang/elasticsearch-shanghai-zone:7.0.1```
## 环境变量(Environment Variables)
```cluster.name```
Elasticsearch集群名称,运行Skywalking需要与此名称保持一致。
cluster.name: "docker-cluster"
network.host: 0.0.0.0
# minimum_master_nodes need to be explicitly set when bound on a public IP
# set to 1 to allow single node clusters
# Details: https://github.com/elastic/elasticsearch/pull/17288
discovery.zen.minimum_master_nodes: 1
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment