Normal Pulled 2m15s kubelet, Successfully pulled image "rancher/klipper-helm:v0.1.5" Normal Pulling 2m23s kubelet, Pulling image "rancher/klipper-helm:v0.1.5"
Normal Scheduled default-scheduler Successfully assigned kube-system/helm-install-traefik-mh72n to var/run/secrets/kubernetes.io/serviceaccount from helm-traefik-token-79kxw (ro)
# k3s kubectl -namespace=kube-system describe pod helm-install-traefik-mh72n Warning BackOff 6s (x5 over 53s) kubelet, Back-off restarting failed container Normal Started 8s (x4 over 57s) kubelet, Started container local-path-provisioner Normal Created 8s (x4 over 57s) kubelet, Created container local-path-provisioner Normal Pulled 8s (x3 over 55s) kubelet, Container image "rancher/local-path-provisioner:v0.0.11" already present on machine Normal Pulled 60s kubelet, Successfully pulled image "rancher/local-path-provisioner:v0.0.11" Normal Pulling 64s kubelet, Pulling image "rancher/local-path-provisioner:v0.0.11" Normal Scheduled default-scheduler Successfully assigned kube-system/local-path-provisioner-58fb86bdfd-npcxt to Warning FailedScheduling default-scheduler 0/1 nodes are available: 1 node(s) had taints that the pod didn't tolerate. Tolerations: /not-ready:NoExecute for 300s SecretName: local-path-provisioner-service-account-token-sjhkv Type: Secret (a volume populated by a Secret) Local-path-provisioner-service-account-token-sjhkv: Type: ConfigMap (a volume populated by a ConfigMap) var/run/secrets/kubernetes.io/serviceaccount from local-path-provisioner-service-account-token-sjhkv (ro)
POD_NAMESPACE: kube-system (v1:metadata.namespace) Image: rancher/local-path-provisioner:v0.0.11 I tried to kill the deamon, but it pops up again the second I kill it.# k3s kubectl -namespace=kube-system describe pod local-path-provisioner-58fb86bdfd-npcxt Here I am confused, does memcached work? Or is something wrong? So to confirm that memcached doesn't listen on any ports I ran " docker ps -a", and this was the output: CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMESġ16acff4b1aa memcached "docker-entrypoint.s…" 10 minutes ago Created memcacheĪ4e1a6168bca staticwebserver:v3 "/init.sh" 2 weeks ago Up 16 hours 0.0.0.0:8002->80/tcp lucid_mccarthyĪ27174f8a988 staticwebserver:v3 "/init.sh" 2 weeks ago Up 16 hours 0.0.0.0:8001->80/tcp thirsty_shockleyĪs I can't see that the container(memcached) listens to any ports I wanted to see what process is already listening on port 11211. In the end it says the port chosen is taken already.
#Error starting dyn updater error starting backend daemon driver
This is the error that comes after running the command above docker: Error response from daemon: driver failed programming external connectivity on endpoint memcache (9f4bd30f7253ee185f6a160ef8e89d3f3c2d46f0361ec15f11a6975477c19430): Error starting userland proxy: listen tcp 0.0.0.0:11211: bind: address already in use. I get an error when I run: docker run -name=memcache -p 11211:11211 -d memcached memcached -m 128 I am having problems setting up memcached on my docker.
0 kommentar(er)
