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: error trying to connect: dns error: Success (os error 85) when running on cluster #3317

Open
KaiWalter opened this issue Apr 2, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@KaiWalter
Copy link

Summary

When trying to call an (AKS cluster) internal service or an external service like

    let url =
        url::Url::parse("http://eu.httpbin.org/ip").map_err(|e| ServiceError::ParseError(e))?;
    tracing::info!("test url {}", url);

    let response = reqwest::Client::new()
        .get(url)
        .send()
        .await
        .map_err(|e| ServiceError::ReqwestError(e))?
        .text()
        .await
        .map_err(|e| ServiceError::ReqwestError(e))?;

I get this error when running on a cluster - with local wasmedge run the call is succeeding.

error sending request for url (http://eu.httpbin.org/ip): error trying to connect: dns error: Success (os error 85)

Current State

I install #wasmedge 0.3.0 with #kwasm node installer ghcr.io/kwasm/kwasm-node-installer:v0.3.1 on AKS,

add a runtime class,

apiVersion: node.k8s.io/v1
kind: RuntimeClass
metadata:
  name: wasmedge-v1
handler: wasmedge
scheduling:
  nodeSelector:
    agentpool: wasm

deploy a service with #knative-serving,

apiVersion: serving.knative.dev/v1
kind: Service
metadata:
  name: distributor
  namespace: default
spec:
  template:
    spec:
      runtimeClassName: wasmedge-v1
      timeoutSeconds: 1
      containers:
        - name: http-server
          image: { will be replaced by deployment script }
          ports:
            - containerPort: 8080
              protocol: TCP
          livenessProbe:
            tcpSocket:
              port: 8080
  traffic:
    - latestRevision: true
      percent: 100

Expected State

I expect DNS resolution of cluster is applied and call to internal and external services is succeeding.

Reproduction steps

  1. Build with options : wasmedge compile target/wasm32-wasi/release/warpwasi_dapr_rs.wasm target/warpwasi_dapr_rs.wasm
  2. Execute with flags : see call to WasmEdge SDK in runwasi containerd shim
  3. Execute with inputs : n.a.
  4. Get error

infrastructure: https://github.com/ZEISS/enterprise-wasm/tree/knative/infra/aks-kn-dapr
module: https://github.com/ZEISS/enterprise-wasm/tree/knative/samples/warpwasi-dapr-rs

Screenshots

No response

Any logs you want to share for showing the specific issue

No response

Components

Rust SDK

WasmEdge Version or Commit you used

0.13.5

Operating system information

CBL-Mariner/Linux

Hardware Architecture

arm64

Compiler flags and options

No response

@KaiWalter KaiWalter added the bug Something isn't working label Apr 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant