[Bug] Docker - ConfigNodeClient:255 - The current node may have been down TEndPoint

[MRIIOT]

Search before asking

• I searched in the issues and found nothing similar.

Version

1.1.2-standalone

Describe the bug and provide the minimal reproduce step

  iotdb:
    container_name: iotdb
    image: apache/iotdb:latest
    restart: always
    networks:
      - net1
    #ports:
    #  - "6667:6667/tcp"
    environment:
      - cn_internal_address=iotdb
      - cn_internal_port=10710
      - cn_consensus_port=10720
      - cn_target_config_node_list=iotdb:10710
      - dn_rpc_address=iotdb
      - dn_internal_address=iotdb
      - dn_rpc_port=6667
      - dn_mpp_data_exchange_port=10740
      - dn_schema_region_consensus_port=10750
      - dn_data_region_consensus_port=10760
      - dn_target_config_node_list=iotdb:10710
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /etc/timezone:/etc/timezone:ro
      - /home/user/volumes/iotdb/data:/iotdb/data
      - /home/user/volumes/iotdb/logs:/iotdb/logs
    labels:
      - traefik.enable=false
    logging:
      driver: "json-file"
      options:
        max-size: "20m"

What did you expect to see?

Successful startup.

What did you see instead?

ConfigNodeClient:255 - The current node may have been down TEndPoint(ip:iotdb, port:10710),try next node

Anything else?

No response

Are you willing to submit a PR?

• I'm willing to submit a PR!

[github-actions]

Hi, this is your first issue in IoTDB project. Thanks for your report. Welcome to join the community!

[changxue2022]

There are some errors in this docker compose file above.

1. iotdb:10710 , iotdb is not the service name. It is the hostname of docker. (see the image below)
2. the network seems not so correct
   detail see
   https://iotdb.apache.org/UserGuide/V1.1.x/QuickStart/WayToGetIoTDB.html#installation-by-docker
   

[MRIIOT]

Thank you. Changing all my iotdb to iotdb-service works.