Replies: 3 comments
-
can you exec into your docker container and see if |
Beta Was this translation helpful? Give feedback.
0 replies
-
try add s3_config.force_path_style(true) |
Beta Was this translation helpful? Give feedback.
0 replies
-
Similar error happend here as well on my EC2, I have a rust program working in Ubuntu EC2 to deal with s3 files, Error: DispatchFailure(
DispatchFailure {
source: ConnectorError {
kind: Io,
source: hyper::Error(
Connect, ConnectError(
"dns error",
Os {
code: 24, kind: Uncategorized, message: "Too many open files"
}
)
),
connection: Unknown
}
}
) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am unable to make request using rust application on docker container deployed to EC2.
It works perfectly on localhost but when I deploy it, I get DisptachFailure with dns error.
I enabled tracing to see if endpoint url was maybe incorrect but the request was identical to the one on my computer except of os. I have all incoming and outgoing ports open for debugging.
I have a reverse proxy in the front but I don't think it has anything to do with this as I never had any problem making outbound request from application inside the containers before, but I am not 100%.
The error
I am using the code below
Is there something that I am overlooking?
I can't use any S3 services in my setup because of this issue.
Beta Was this translation helpful? Give feedback.
All reactions