solo-io / wasm

Web Assembly tools and SDKs for extending cloud-native infrastructure
Apache License 2.0
305 stars 39 forks source link

wasme deploy istio always report tcp :8080: bind: address already in use #128

Open hobbytp opened 4 years ago

hobbytp commented 4 years ago

Problem

When I use wasme to deploy istio, it always return "Error: error listening on :8080: listen tcp :8080: bind: address already in use"

Reproduce Steps

Step1: install istio 1.5.2 Step2: install bookinfo demo to namespace hobby Step3: deploy wasm as below, and always failed.

$ wasme deploy istio webassemblyhub.io/hobby/add-header:v0.1 \

--id=myfilter \
--namespace hobby \
--config 'world'

INFO[0000] cache namespace already exists cache=wasme-cache.wasme image="quay.io/solo-io/wasme:0.0.20" INFO[0000] cache configmap already exists cache=wasme-cache.wasme image="quay.io/solo-io/wasme:0.0.20" INFO[0000] cache service account already exists cache=wasme-cache.wasme image="quay.io/solo-io/wasme:0.0.20" INFO[0000] cache role updated cache=wasme-cache.wasme image="quay.io/solo-io/wasme:0.0.20" INFO[0000] cache rolebinding updated cache=wasme-cache.wasme image="quay.io/solo-io/wasme:0.0.20" INFO[0000] cache daemonset updated cache=wasme-cache.wasme image="quay.io/solo-io/wasme:0.0.20" Error: error listening on :8080: listen tcp :8080: bind: address already in use Usage: wasme deploy istio --id= [--config=] [--root-id=] [--namespaces ] [--name deployment-name] [flags]

Lab Environment

$ sudo minikube version minikube version: v1.11.0 commit: 57e2f55f47effe9ce396cea42a1e0eb4f611ebbd

$ kubectl version Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.0", GitCommit:"9e991415386e4cf155a24b1da15becaa390438d8", GitTreeState:"clean", BuildDate:"2020-03-25T14:58:59Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.3", GitCommit:"2e7996e3e2712684bc73f0dec0200d64eec7fe40", GitTreeState:"clean", BuildDate:"2020-05-20T12:43:34Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}

Sodman commented 3 years ago

Hi @hobbytp , are you still experiencing this issue with the latest version of wasme? That error message implies that something else is already running on port 8080. Are you running another server on that port perhaps?