-
Notifications
You must be signed in to change notification settings - Fork 245
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
Hyper dns error when using docker #1138
Comments
Hello @ripls56, it turns out we struggled with this. TL;DR it turns out that MinIO supports S3's path-style by default (which AWS will deprecate) whereas the S3 sdk goes for virtual-hosted-style instead by default and that's where you see those DNS errors. So you might want to force path_style like so. Also note that your particular local DNS resolver (OS level) and docker listen/host configuration (i.e: listening to Hope that helps! |
Hi @brainstorm, thanks for your help. Everything is working now, but am I right in understanding that I can't create buckets at runtime because there will be no associated names for them in the docker? (if I don't use path_style) |
Comments on closed issues are hard for our team to see. |
I haven't tested that particular bit since our buckets are pre-created... but I'd guess you can create them at runtime, you just have to adjust the style/how to reach them? Fire up a wireshark/tshark packet inspector and you'll probably see DNS requests failing and then you can fix it up from there. |
#132) Closes #131, where I discovered the `localstack` example is broken when running: ``` cargo run --example localstack --features="localstack" ``` Some research brought me to [awslabs/aws-sdk-rust#1138](awslabs/aws-sdk-rust#1138), which uncovered that `create_bucket` is broken here because `localstack` uses the soon-to-be-deprecated ["path-style"](https://aws.amazon.com/blogs/aws/amazon-s3-path-deprecation-plan-the-rest-of-the-story/) address style rather than the newer "virutal-hosted" style. I reworked the configuration in the example to set `force_path_style(true)`, which fixes `create_bucket`. The example now runs successfully. I also updated the `BehaviorVersion`, because the currently referenced one is now deprecated and was causing a warning.
Describe the bug
Good afternoon, when trying to connect by url address, if I use docker I get an error related to dns.
Expected Behavior
Url address is recognised and I can access the storage.
Current Behavior
Url address is not recognised
Error:
Reproduction Steps
compose.yaml
main.rs
Cargo.toml
Possible Solution
No response
Additional Information/Context
I also tried localstack to exclude any problems with minio.
However, it works if you access the storage outside the docker network (i.e. only the storage is deployed)
Also I am confused that the access to the bucket goes through the sub domain (attached in the logs), I am a beginner so I don't know how it should be 😔
Version
Environment details (OS name and version, etc.)
macOS 14.4.1 23E224 darwin-arm64
Logs
The text was updated successfully, but these errors were encountered: