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]: Unable to connect to minio in standalone mode installed in Docker #32265

Open
1 task done
yesletgo opened this issue Apr 15, 2024 · 6 comments
Open
1 task done
Assignees
Labels
kind/bug Issues or changes related a bug stale indicates no udpates for 30 days triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@yesletgo
Copy link

yesletgo commented Apr 15, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Environment

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

Current Behavior

error="Get " appears http://localhost:9000/a -Bucket/? Location=\“

Expected Behavior

can connect minio:9000

Steps To Reproduce

I installed it through the following methods:
Wget https://raw.githubusercontent.com/milvus-io/milvus/master/scripts/standalone_embed.sh
Bash standalone embedded. sh start

All are default configurations, so how does mini connect?
Mini:
Address: localhost # Address of MinIO/S3
Port: 9000 # Port of MinIO/S3
AccessKeyID: minioadmin # accessKeyID of MinIO/S3
SecretAccess Key: minioadmin # MinIO/S3 encryption string
UseSSL: false # Access to MinIO/S3 with SSL
BucketName: a-bucket # Bucket name in MinIO/S3
RootPath: files # The root path where the message is stored in MinIO/S3

I also added port mapping, but I couldn't connect.
![image](https://github.com/milvus-io/milvus/assets/21998052/4d99411d-5b57-45b7-9754-c63bb6182431)


Milvus Log

No response

Anything else?

No response

@yesletgo yesletgo 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 Apr 15, 2024
@zhuwenxing
Copy link
Contributor

standalone_embed uses local storage as backend storage, so no minio was installed.
you can follow this link (https://milvus.io/docs/install_standalone-docker-compose.md) to setup

@yesletgo
Copy link
Author

standalone_embed uses local storage as backend storage, so no minio was installed. you can follow this link (https://milvus.io/docs/install_standalone-docker-compose.md) to setup

If I just want to use the standalone embedded mode, how do I backup it?

@yanliang567
Copy link
Contributor

I'd suggest you not use standalone emedded in this case

standalone_embed uses local storage as backend storage, so no minio was installed. you can follow this link (https://milvus.io/docs/install_standalone-docker-compose.md) to setup

If I just want to use the standalone embedded mode, how do I backup it?

/asign @yesletgo

@yanliang567 yanliang567 added triage/needs-information Indicates an issue needs more information in order to work on it. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Apr 15, 2024
@yanliang567
Copy link
Contributor

/assign @yesletgo
/unassign

@sre-ci-robot sre-ci-robot assigned yesletgo and unassigned yanliang567 Apr 16, 2024
@yesletgo
Copy link
Author

I'd suggest you not use standalone emedded in this case

standalone_embed uses local storage as backend storage, so no minio was installed. you can follow this link (https://milvus.io/docs/install_standalone-docker-compose.md) to setup

If I just want to use the standalone embedded mode, how do I backup it?

/asign @yesletgo

Why is it not suitable in this example? Does standalone'embed not require backup, or may I ask how to recover it if there is a malfunction?

Copy link

stale bot commented May 18, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Rotten issues close after 30d of inactivity. Reopen the issue with /reopen.

@stale stale bot added the stale indicates no udpates for 30 days label May 18, 2024
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 stale indicates no udpates for 30 days triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Development

No branches or pull requests

3 participants