[Bug] 无法启动 iotdb:1.0.1-standalone

### Search before asking

- [X] I searched in the [issues](https://github.com/apache/iotdb/issues) and found nothing similar.

### Version

iotdb:1.0.1-standalone

### Describe the bug and provide the minimal reproduce step

docker network create --driver=bridge --subnet=172.18.0.0/27 --gateway=172.18.0.1 iotdb

docker run --name iotdb-service \
--hostname iotdb-service \
--network iotdb \
--ip 172.18.0.6 \
-p 6667:6667 \
-e cn_internal_address=iotdb-service \
-e cn_target_config_node_list=iotdb-service:22277 \
-e dn_rpc_address=iotdb-service \
-e dn_internal_address=iotdb-service \
-e dn_target_config_node_list=iotdb-service:22277 \
apache/iotdb:1.0.1-standalone

### What did you expect to see?

无法启动单节点模式的iotdb 服务

### What did you see instead?

[main] WARN o.a.i.d.c.ConfigNodeClient:259 - The current node may have been down TEndPoint(ip:iotdb-service, port:22277),try next node
[main] WARN o.a.i.db.service.DataNode:240 - Cannot pull system configurations from ConfigNode-leader, because: Fail to connect to any config node. Please check status of ConfigNodes

### Anything else?

_No response_

### Are you willing to submit a PR?

- [ ] I'm willing to submit a PR!

Inizia riproducendo la rete Docker fornita e il comando `apache/iotdb:1.0.1-standalone`, quindi esamina il percorso di avvio intorno ai punti di ingresso registrati `ConfigNodeClient` e `DataNode`. Il lavoro è concluso quando il servizio IoTDB a nodo singolo si avvia correttamente e si connette al proprio ConfigNode senza gli avvisi segnalati.

Scritto dal modello di indicizzazione a partire dal testo della issue.