(!)ERROR:: failed to get client address [error="find no available rootcoord, check rootcoord state"

[Zy1bREAd]

Version: 2.5.27
docker-compose deploy

no local minio, OSS is Tencent COS, but start Milvus occur error.
rootcoord is not running, I think about Tencent COS Config,Pleases Check!!!

milvus.yaml (core config)
The Tencent COS region is bangkok,milvus-backup is OK!

Tips： Except for the changes made to the COS configuration, all others are set to the default values.
`

minio:
address: cos.ap-bangkok.myqcloud.com
port: 443 # Port of MinIO or S3 service.
accessKeyID: "XXXXX"
secretAccessKey: "XXXXX"
useSSL: false
ssl:
tlsCACert: /path/to/public.crt
bucketName: prod-intl-milvus-xxxx
rootPath: prod-data
region: ap-bangkok
`

docker-compose.yaml:
`
version: '3.5'

services:
etcd:
container_name: milvus-etcd
image: quay.io/coreos/etcd:v3.5.18
environment:
- ETCD_AUTO_COMPACTION_MODE=revision
- ETCD_AUTO_COMPACTION_RETENTION=1000
- ETCD_QUOTA_BACKEND_BYTES=4294967296
- ETCD_SNAPSHOT_COUNT=50000
volumes:
- /data/milvus/etcd:/etcd
command: etcd -advertise-client-urls=http://etcd:2379 -listen-client-urls http://0.0.0.0:2379 --data-dir /etcd
healthcheck:
test: ["CMD", "etcdctl", "endpoint", "health"]
interval: 30s
timeout: 20s
retries: 3

minio:

  #  ...

standalone:
container_name: milvus-standalone
image: milvusdb/milvus:v2.5.27
command: ["milvus", "run", "standalone"]
security_opt:
- seccomp:unconfined
environment:
etcd_endpoints: etcd:2379
#minio_address: minio:9000
volumes:
- /data/milvus/milvus:/var/lib/milvus
healthcheck:
test: ["CMD", "curl", "-f", "http://localhost:9091/healthz"]
interval: 30s
start_period: 90s
timeout: 20s
retries: 3
ports:
- "29530:19530"
- "29091:9091"
depends_on:
- "etcd"

networks:
default:
name: milvus
`

docker-compose logs file output:
debug_milvus_tencent_cos.log

[yhmo]

[2026/04/30 09:03:33.970 +00:00] [WARN] [storage/minio_object_storage.go:151] ["failed to check blob bucket exist"] [bucket=a-bucket] [error="Get \"http://localhost:9000/a-bucket/?location=\": dial tcp [::1]:9000: connect: connection refused"]

Seems the remote storage is not correctly configured, it still trying to connect the local minio by this address "http://localhost:9000/a-bucket".

To configure the remote object storage, you need to override the milvus.yaml in the docker-compose.yaml.
For example, this line "- ${DOCKER_VOLUME_DIRECTORY:-.}/milvus.yaml:/milvus/configs/milvus.yaml" maps the milvus.yaml to outside the container(${DOCKER_VOLUME_DIRECTORY is the path of docker-compose.yaml).

  standalone:
    container_name: milvus-standalone
    image: milvusdb/milvus:v2.5.27
    ......
    volumes:
      - ${DOCKER_VOLUME_DIRECTORY:-.}/volumes/milvus:/var/lib/milvus
      - ${DOCKER_VOLUME_DIRECTORY:-.}/milvus.yaml:/milvus/configs/milvus.yaml

And then modify the ${DOCKER_VOLUME_DIRECTORY:-.}/milvus.yaml to configure your remote object storage.

[Zy1bREAd]

but this is my milvus.yaml config setting:

minio:
address: cos.ap-bangkok.myqcloud.com
port: 443 # Port of MinIO or S3 service.
accessKeyID: "XXXXX"
secretAccessKey: "XXXXX"
useSSL: false
ssl:
tlsCACert: /path/to/public.crt
bucketName: prod-intl-milvus-xxxx
rootPath: prod-data
region: ap-bangkok

Tips： The docker-compose yaml configuration has been completed, and the milvus.yaml configuration has also been done.

[yhmo]

Is there any log like this "[WARN] [storage/minio_object_storage.go:151] ["failed to check blob bucket exist"]" in the container log?