testcontainers / testcontainers/testcontainers-rs-modules-community
DispatchFailure in the LocalStack example
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 174
- Forks
- 88
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
Running the LocalStack example using cargo run --example localstack --features="localstack" leads to the following error:
Error: DispatchFailure(DispatchFailure { source: ConnectorError { kind: Io, source: hyper_util::client::legacy::Error(Connect, ConnectError("tcp connect error", 127.0.0.1:37097, Os { code: 61, kind: ConnectionRefused, message: "Connection refused" })), connection: Unknown } })
This is on a freshly cloned repository on the main branch.
Anything I can do to mitigate the error? 😄
To Reproduce
Run cargo run --example localstack --features="localstack".
Expected behavior
The LocalStack container runs as expected and can be reached using an AWS S3 client.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running cargo run --example localstack --features="localstack" and inspect the LocalStack example's container startup and connection handling. The issue is resolved when the container starts successfully and the AWS S3 client can reach it without a DispatchFailure connection-refused error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100