Docker中的Kibana和Elasticsearch与标准安装共存

Question

我正试图在我的服务器上设置一个新版本的Kibana和Elasticsearch。我有一个现有的K和E运行默认端口(5601，9200)，升级现有数据不是一个选项。我想在Docker中运行K和E的较新版本(7.4.2)，使用不同的端口(5611:5601、9211:9200)来访问容器。我有新的数据区可用。

version: '3'

networks:
  elk01:
    driver: bridge

services:
  es01:
    image: elasticsearch:7.4.2
    container_name: es01
    user: "983"
    networks:
      - elk01
    environment:
      #- cluster.initial_master_nodes=es01
      - cluster.name=docker-cluster
      - discovery.type=single-node
      - bootstrap.memory_lock=true
      - "ES_JAVA_OPTS=-Xms4g -Xmx4g -XX:-HeapDumpOnOutOfMemoryError"
      #- ES_JAVA_OPTS: "-Xms4g -Xmx4g -XX:-HeapDumpOnOutOfMemoryError"
    ulimits:
      memlock:
        soft: -1
        hard: -1
    ports:
      - "9211:9200"
      - "9311:9300"
    expose:
      - "9211"
    volumes:
      - /elk/elk7_4_2/elasticsearch/data:/usr/share/elasticsearch/data
      - /elk/elk7_4_2/elasticsearch/logs:/usr/share/elasticsearch/logs

  k01:
    depends_on:
    - es01
    image: kibana:7.4.2
    container_name: k01
    user: "981"
    networks:
      - elk01
    environment:
      - SERVER_NAME=kibana.localhost
      - ELASTICSEARCH_URL=http://es01:9211
      - ELASTICSEARCH_HOST=es01
      - ELASTICSEARCH_PORT=9211
      #- ELASTICSEARCH_USERNAME=elastic
      #- ELASTIC_PWD=changeme
      #- KIBANA_PWD=changeme
      - xpack.security.enabled=false
    ports:
      - "5611:5601"
    expose:
      - "5611"

k01     | {"type":"log","@timestamp":"2019-11-22T22:08:58Z","tags":["reporting","browser-driver","warning"],"pid":8,"message":"Enabling the Chromium sandbox provides an additional layer of protection."}
k01     | {"type":"log","@timestamp":"2019-11-22T22:08:59Z","tags":["error","elasticsearch","admin"],"pid":8,"message":"Request error, retrying\nHEAD http://elasticsearch:9200/.apm-agent-configuration => getaddrinfo ENOTFOUND elasticsearch elasticsearch:9200"}
k01     | {"type":"log","@timestamp":"2019-11-22T22:08:59Z","tags":["error","elasticsearch","admin"],"pid":8,"message":"Request error, retrying\nGET http://elasticsearch:9200/_nodes?filter_path=nodes.*.version%2Cnodes.*.http.publish_address%2Cnodes.*.ip => getaddrinfo ENOTFOUND elasticsearch elasticsearch:9200"}
k01     | {"type":"log","@timestamp":"2019-11-22T22:08:59Z","tags":["warning","elasticsearch","admin"],"pid":8,"message":"Unable to revive connection: http://elasticsearch:9200/"}
k01     | {"type":"log","@timestamp":"2019-11-22T22:08:59Z","tags":["warning","elasticsearch","admin"],"pid":8,"message":"No living connections"}
k01     | {"type":"log","@timestamp":"2019-11-22T22:08:59Z","tags":["status","plugin:xpack_main@7.4.2","error"],"pid":8,"state":"red","message":"Status changed from yellow to red - No Living connections","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"}
k01     | {"type":"log","@timestamp":"2019-11-22T22:08:59Z","tags":["status","plugin:graph@7.4.2","error"],"pid":8,"state":"red","message":"Status changed from yellow to red - No Living connections","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"}

Answer 1

您应该从elasticsearch容器中公开端口9200，因为ES正在使用9200 dockers端口。另外，kibana正在另一个容器中运行，它只能看到来自另一个容器的暴露端口，在本例中应该是9200。

有关更多细节，请查看docker-compose端口与expose端口之间的区别