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: DNS not resolving service name to IP address #23

Closed
hydai opened this issue Feb 19, 2024 · 8 comments · Fixed by #24
Closed

bug: DNS not resolving service name to IP address #23

hydai opened this issue Feb 19, 2024 · 8 comments · Fixed by #24
Assignees

Comments

@hydai
Copy link
Member

hydai commented Feb 19, 2024

Related issue:

  1. DNS not resolving service name to IP address in a Rust compiled to WASM container moby/moby#47403
  2. Fix DNS error on WASM adding static IPs to every container on a new network #22

The current status:

  1. WASM container cannot resolve the service name
  2. The DNS server of docker-compose is still 127.0.0.11:53
  3. The DNS_SERVER magic is not working.
  4. The wasi-socket component inside WasmEdge is not changed.
  5. We should check all used wasi-socket crates to see if there are some modifications related to this problem <-- We are here now
@aalonsolopez
Copy link
Contributor

My understanding of Rust is super basic, but I was planning on learning it... Something in which I can help?

@hydai
Copy link
Member Author

hydai commented Feb 20, 2024

The related code is under these three crates: https://github.com/second-state/microservice-rust-mysql/blob/main/Cargo.toml#L11-L13

If you would like to dig into the details, please check the error caused in the microservice-rust-mysql and find which crates are highly related to the error.

@aalonsolopez
Copy link
Contributor

Perfect!

@aalonsolopez
Copy link
Contributor

Can you assign this to me? i will try my best to solve it. If I can't, I'll let you know.

@hydai
Copy link
Member Author

hydai commented Feb 21, 2024

Sure. Here you go.

@aalonsolopez
Copy link
Contributor

aalonsolopez commented Feb 26, 2024

I'm nearly 99% sure that the problem is with tokio_wasi crate, making some tests rn

@aalonsolopez
Copy link
Contributor

As you can see in WasmEdge/tokio@f6dae1c this problem seems to be solved, but anyway it still failing. Apparently, it has like version conflicts because the repo references 1.28.2 as the latest version but it's not published on crates.io

@aalonsolopez
Copy link
Contributor

#24 has the solution

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants