Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
1 task done
wrl02 opened this issue Jan 16, 2025 · 1 comment
Open
1 task done

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

wrl02 opened this issue Jan 16, 2025 · 1 comment
Assignees
Labels
kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@wrl02
Copy link

wrl02 commented Jan 16, 2025

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

@wrl02 wrl02 added kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jan 16, 2025
@xiaofan-luan
Copy link
Collaborator

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

3 participants