[Bug]: change MINIO_SECRET_KEY, milvus-standalone cant start

[wrl02]

Is there an existing issue for this?

• I have searched the existing issues

Environment

- Milvus version:
- Deployment mode(standalone or cluster):
- MQ type(rocksmq, pulsar or kafka):    
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

I want to modify the MinIO initial password, but after modifying the yml file, the milvus-standalone container fails to start, how should I modify the MinIO initial password?

services：
minio：
...
environment:
MINIO_ACCESS_KEY:new_access_key
MINIO_SECRECT_KEY:new_secrect_key
...

Expected Behavior

No response

Steps To Reproduce

Milvus Log

No response

Anything else?

No response

[xiaofan-luan]

that should be good enough if u use the right minio AK/SK
what's the error you get?

[wrl02]

that should be good enough if u use the right minio AK/SK what's the error you get?
services:
etcd:
container_name: milvus-etcd
image: quay.io/coreos/etcd:v3.5.14
environment:
- ETCD_AUTO_COMPACTION_MODE=revision
- ETCD_AUTO_COMPACTION_RETENTION=1000
- ETCD_QUOTA_BACKEND_BYTES=4294967296
- ETCD_SNAPSHOT_COUNT=50000
volumes:
- ${DOCKER_VOLUME_DIRECTORY:-.}/volumes/etcd:/etcd
command: etcd -advertise-client-urls=http://127.0.0.1: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:
container_name: milvus-minio
image: minio/minio:RELEASE.2023-03-20T20-16-18Z
environment:
MINIO_ACCESS_KEY: new_access_key
MINIO_SECRET_KEY: new_secrect_key

ports:
  - "9005:9005"
volumes:
  - ${DOCKER_VOLUME_DIRECTORY:-.}/volumes/minio:/minio_data
command: minio server /minio_data --console-address ":9005"
healthcheck:
  test: ["CMD", "curl", "-f", "http://localhost:9000/minio/health/live"]
  interval: 30s
  timeout: 20s
  retries: 3

standalone:
container_name: milvus-standalone
image: milvusdb/milvus:v2.5.1
command: ["milvus", "run", "standalone"]
security_opt:
- seccomp:unconfined
environment:
ETCD_ENDPOINTS: etcd:2379
MINIO_ADDRESS: minio:9000

volumes:
  - ${DOCKER_VOLUME_DIRECTORY:-.}/volumes/milvus:/var/lib/milvus
healthcheck:
  test: ["CMD", "curl", "-f", "http://localhost:9091/healthz"]
  interval: 30s
  start_period: 90s
  timeout: 20s
  retries: 3
ports:
  - "19530:19530"
  - "9091:9091"
depends_on:
  - "etcd"
  - "minio"

networks:
default:
name: milvus

i dont kmow why milvus-standalone fails to start

milvus$docker compose ps
NAME IMAGE COMMAND SERVICE CREATED STATUS PORTS
milvus-etcd quay.io/coreos/etcd:v3.5.14 "etcd -advertise-cli…" etcd 45 seconds ago Up 44 seconds (healthy) 2379-2380/tcp
milvus-minio minio/minio:RELEASE.2023-03-20T20-16-18Z "/usr/bin/docker-ent…" minio 45 seconds ago Up 44 seconds (healthy) 9000/tcp, 0.0.0.0:9005->9005/tcp, :::9005->9005/tcp
milvus-standalone milvusdb/milvus:v2.5.1 "/tini -- milvus run…" standalone 45 seconds ago Up 43 seconds (health: starting) 0.0.0.0:9091->9091/tcp, :::9091->9091/tcp, 0.0.0.0:19530->19530/tcp, :::19530->19530/tcp
milvus$ docker compose ps
NAME IMAGE COMMAND SERVICE CREATED STATUS PORTS
milvus-etcd quay.io/coreos/etcd:v3.5.14 "etcd -advertise-cli…" etcd About a minute ago Up About a minute (healthy) 2379-2380/tcp
milvus-minio minio/minio:RELEASE.2023-03-20T20-16-18Z "/usr/bin/docker-ent…" minio About a minute ago Up About a minute (healthy) 9000/tcp, 0.0.0.0:9005->9005/tcp, :::9005->9005/tcp

[yanliang567]

/assign @LoveEachDay
/unassign