% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  3103  100  3103    0     0   8753      0 --:--:-- --:--:-- --:--:--  8765
docker: Error response from daemon: grpc: the connection is unavailable.
time="2019-06-25T14:57:25+02:00" level=error msg="error getting events from daemon: net/http: request canceled"
Error: Get https://10.6.225.82:8443/api/v1/namespaces/kube-system/pods?labelSelector=app%3Dhelm%2Cname%3Dtiller: dial tcp 10.6.225.82:8443: connect: connection refused
The connection to the server 10.6.225.82:8443 was refused - did you specify the right host or port?
The connection to the server 10.6.225.82:8443 was refused - did you specify the right host or port?
The connection to the server 10.6.225.82:8443 was refused - did you specify the right host or port?
The connection to the server 10.6.225.82:8443 was refused - did you specify the right host or port?
The connection to the server 10.6.225.82:8443 was refused - did you specify the right host or port?
Error response from daemon: Cannot kill container eb413392000c: Container eb413392000c1a29ae58942cc1db8e265b3c98716a808457a610ec4c4c09d73f is not running
Error response from daemon: Cannot kill container 0bcca8f7529d: Cannot kill container 0bcca8f7529dd55f5ad033c95a36950379f46ce91f4a9a7badd1882af813b15b: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Could not kill running container 0bcca8f7529dd55f5ad033c95a36950379f46ce91f4a9a7badd1882af813b15b, cannot remove - Cannot kill container 0bcca8f7529dd55f5ad033c95a36950379f46ce91f4a9a7badd1882af813b15b: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Cannot kill container cf41be87de1a: Cannot kill container cf41be87de1abb2f260b7f4ef10cf6197a8f759a62ae151ed98c6ec81bdbfc68: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Could not kill running container cf41be87de1abb2f260b7f4ef10cf6197a8f759a62ae151ed98c6ec81bdbfc68, cannot remove - Cannot kill container cf41be87de1abb2f260b7f4ef10cf6197a8f759a62ae151ed98c6ec81bdbfc68: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Cannot kill container bebc3b3ec129: Cannot kill container bebc3b3ec129551e08ab91fefb7b055dae06ef2510f3a13a1644f0a68e88a957: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Could not kill running container bebc3b3ec129551e08ab91fefb7b055dae06ef2510f3a13a1644f0a68e88a957, cannot remove - Cannot kill container bebc3b3ec129551e08ab91fefb7b055dae06ef2510f3a13a1644f0a68e88a957: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Cannot kill container afbddad4467f: Cannot kill container afbddad4467f5267aa0154f0f6b4e4504497051872cf9148d2c7f54bf5315d08: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Could not kill running container afbddad4467f5267aa0154f0f6b4e4504497051872cf9148d2c7f54bf5315d08, cannot remove - Cannot kill container afbddad4467f5267aa0154f0f6b4e4504497051872cf9148d2c7f54bf5315d08: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Cannot kill container c7bebd9b7a4f: Cannot kill container c7bebd9b7a4f3b1292d31dd7b852b12b763f0df5ef2f9413b4b18e7cdf577a41: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Could not kill running container c7bebd9b7a4f3b1292d31dd7b852b12b763f0df5ef2f9413b4b18e7cdf577a41, cannot remove - Cannot kill container c7bebd9b7a4f3b1292d31dd7b852b12b763f0df5ef2f9413b4b18e7cdf577a41: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Cannot kill container 31bdc12941fa: Cannot kill container 31bdc12941fac77ec24fef819b798d53a66f9c85c771ca21a37df6a65709d006: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Could not kill running container 31bdc12941fac77ec24fef819b798d53a66f9c85c771ca21a37df6a65709d006, cannot remove - Cannot kill container 31bdc12941fac77ec24fef819b798d53a66f9c85c771ca21a37df6a65709d006: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Cannot kill container 9a84c52e5bcf: Cannot kill container 9a84c52e5bcf7d67e07fa2573a48330af8d4c9b11751bf56179684af5c91cb4a: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Could not kill running container 9a84c52e5bcf7d67e07fa2573a48330af8d4c9b11751bf56179684af5c91cb4a, cannot remove - Cannot kill container 9a84c52e5bcf7d67e07fa2573a48330af8d4c9b11751bf56179684af5c91cb4a: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Cannot kill container 48eeffce3bc9: Cannot kill container 48eeffce3bc974257408d0dac3663b7101115cb3d7450b7d09e9f44475b90b60: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Could not kill running container 48eeffce3bc974257408d0dac3663b7101115cb3d7450b7d09e9f44475b90b60, cannot remove - Cannot kill container 48eeffce3bc974257408d0dac3663b7101115cb3d7450b7d09e9f44475b90b60: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Cannot kill container 23fa860c5158: Cannot kill container 23fa860c51588263392b6496b0e66b44a12ef931255dd628d9c77c3c92129124: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Could not kill running container 23fa860c51588263392b6496b0e66b44a12ef931255dd628d9c77c3c92129124, cannot remove - Cannot kill container 23fa860c51588263392b6496b0e66b44a12ef931255dd628d9c77c3c92129124: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Cannot kill container b41447545dbe: Cannot kill container b41447545dbedd64f9bed289c6ba903a214b8b43de2f443553a0987f45f5625c: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Could not kill running container b41447545dbedd64f9bed289c6ba903a214b8b43de2f443553a0987f45f5625c, cannot remove - Cannot kill container b41447545dbedd64f9bed289c6ba903a214b8b43de2f443553a0987f45f5625c: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Cannot kill container fb2446ae2ca9: Cannot kill container fb2446ae2ca9105ae2889e7c62454065533a4657c2a1ff06a49b113632e5eb45: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Could not kill running container fb2446ae2ca9105ae2889e7c62454065533a4657c2a1ff06a49b113632e5eb45, cannot remove - Cannot kill container fb2446ae2ca9105ae2889e7c62454065533a4657c2a1ff06a49b113632e5eb45: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Cannot kill container 8d2c8afd0f9f: Cannot kill container 8d2c8afd0f9f29153a06c893cbdb0432214a5a0e15380223bb58a8bd4aa0074a: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Could not kill running container 8d2c8afd0f9f29153a06c893cbdb0432214a5a0e15380223bb58a8bd4aa0074a, cannot remove - Cannot kill container 8d2c8afd0f9f29153a06c893cbdb0432214a5a0e15380223bb58a8bd4aa0074a: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Cannot kill container b9ffe28e0acd: Cannot kill container b9ffe28e0acdc15285486253491b2d3221853c822a600802dfc6fe6c19f60c24: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Could not kill running container b9ffe28e0acdc15285486253491b2d3221853c822a600802dfc6fe6c19f60c24, cannot remove - Cannot kill container b9ffe28e0acdc15285486253491b2d3221853c822a600802dfc6fe6c19f60c24: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Cannot kill container db831e2086ab: Cannot kill container db831e2086abff4b5490283be8361a3716a33e2135bafc7ade06b6ae65f26f0b: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Could not kill running container db831e2086abff4b5490283be8361a3716a33e2135bafc7ade06b6ae65f26f0b, cannot remove - Cannot kill container db831e2086abff4b5490283be8361a3716a33e2135bafc7ade06b6ae65f26f0b: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: unable to remove volume: remove 137c45e8754a844e25c66d419c67e6172070e9c6a6e916309294ab1a17ed6177: volume is in use - [afbddad4467f5267aa0154f0f6b4e4504497051872cf9148d2c7f54bf5315d08]
Error response from daemon: unable to remove volume: remove 1cba6fa3dcd34d5f422676927ac99c2447a7099df101ad4beb6379acd2e22f5e: volume is in use - [bebc3b3ec129551e08ab91fefb7b055dae06ef2510f3a13a1644f0a68e88a957]
Error response from daemon: unable to remove volume: remove 2f3274020e9dd83c0f8f926646337f21c7e3ffa1cc948869cac3e9a569fcb2a0: volume is in use - [48eeffce3bc974257408d0dac3663b7101115cb3d7450b7d09e9f44475b90b60]
Error response from daemon: unable to remove volume: remove 35de45e116fc02322e3145a2932e8a245f60a697845e75397f6b221c5967c077: volume is in use - [8d2c8afd0f9f29153a06c893cbdb0432214a5a0e15380223bb58a8bd4aa0074a]
Error response from daemon: unable to remove volume: remove 3aedc2b63acb146418dfabe0523cc919277e2e6b3d5c663a4597d41a3b3a6452: volume is in use - [fb2446ae2ca9105ae2889e7c62454065533a4657c2a1ff06a49b113632e5eb45]
Error response from daemon: unable to remove volume: remove 3dd7008c7991d747309ac69c9f1c5e6907c3b763e73a1a63b16c50cb7ff2426c: volume is in use - [b41447545dbedd64f9bed289c6ba903a214b8b43de2f443553a0987f45f5625c]
Error response from daemon: unable to remove volume: remove 53010c6640bab65f9bf1b3b085bb7c3a7376ad1faf4f622fdb2b057c56704668: volume is in use - [8d2c8afd0f9f29153a06c893cbdb0432214a5a0e15380223bb58a8bd4aa0074a]
Error response from daemon: unable to remove volume: remove 67e33d7d0bae815556903422081af560ce650d36d3c38d2603799bf53d714172: volume is in use - [c7bebd9b7a4f3b1292d31dd7b852b12b763f0df5ef2f9413b4b18e7cdf577a41]
Error response from daemon: unable to remove volume: remove 6bf08edc84a5423eb5963bca2dabda70c627f9c52a4ed13d1f2a6f46bd0d4b67: volume is in use - [cf41be87de1abb2f260b7f4ef10cf6197a8f759a62ae151ed98c6ec81bdbfc68]
Error response from daemon: unable to remove volume: remove 7256d970c7b4263d74c49e0e83240040c3fc2ae0d440f45ce1bbfc52bb9ea416: volume is in use - [48eeffce3bc974257408d0dac3663b7101115cb3d7450b7d09e9f44475b90b60]
Error response from daemon: unable to remove volume: remove 76596536d8441e1c5f19c66b02145d63a5b42826b0e75a3b37983b536ff6e779: volume is in use - [fb2446ae2ca9105ae2889e7c62454065533a4657c2a1ff06a49b113632e5eb45]
Error response from daemon: unable to remove volume: remove 9a6f603a33cd2a5afd89eb11b371fa4e7308e5fda34a0b1b19594943139b8639: volume is in use - [0bcca8f7529dd55f5ad033c95a36950379f46ce91f4a9a7badd1882af813b15b]
Error response from daemon: unable to remove volume: remove 9af68bada0f6615083e0ecfc122ed722290e68d8a536f27c97983acad38bcf31: volume is in use - [b41447545dbedd64f9bed289c6ba903a214b8b43de2f443553a0987f45f5625c]
Error response from daemon: unable to remove volume: remove 9d01be3708b29d781f41dba18019c06993e68df0bf2505592fd8506e67dad630: volume is in use - [cf41be87de1abb2f260b7f4ef10cf6197a8f759a62ae151ed98c6ec81bdbfc68]
Error response from daemon: unable to remove volume: remove a0d8814d71f31411bdba4c1b143ef255a516ceafd420221b134b61d70cffd945: volume is in use - [9a84c52e5bcf7d67e07fa2573a48330af8d4c9b11751bf56179684af5c91cb4a]
Error response from daemon: unable to remove volume: remove a6f3f84e9d543e2f5e34bd92ea85804240c2b2808bc32f10691f44abaab76706: volume is in use - [b9ffe28e0acdc15285486253491b2d3221853c822a600802dfc6fe6c19f60c24]
Error response from daemon: unable to remove volume: remove ace2eb2ee5bc2d1e02a4710a1d17b17e05d8a7d9fccaa9681cdb9348802ee83a: volume is in use - [31bdc12941fac77ec24fef819b798d53a66f9c85c771ca21a37df6a65709d006]
Error response from daemon: unable to remove volume: remove c1e5f066593d77594ca412ff7b23ac23e84bb4168d63b4730e7ab93d344f270e: volume is in use - [c7bebd9b7a4f3b1292d31dd7b852b12b763f0df5ef2f9413b4b18e7cdf577a41]
Error response from daemon: unable to remove volume: remove c27e21311dec910de623813e70500a3313c3401a72dbd67a051cf415446a2b1d: volume is in use - [9a84c52e5bcf7d67e07fa2573a48330af8d4c9b11751bf56179684af5c91cb4a]
Error response from daemon: unable to remove volume: remove d6770cd825883a029d1a76d32f81cb6a6b1f85832f5cff06188e7ab6c8e3407b: volume is in use - [db831e2086abff4b5490283be8361a3716a33e2135bafc7ade06b6ae65f26f0b]
Error response from daemon: unable to remove volume: remove d79f1baca87a3e525b1161e2386c4d423d699999487b49051d7a2597341f4f2b: volume is in use - [23fa860c51588263392b6496b0e66b44a12ef931255dd628d9c77c3c92129124]
Error response from daemon: unable to remove volume: remove daab064ec0c43f070488a95a526cb66426657ae69277691ee50b92336eb41f4e: volume is in use - [afbddad4467f5267aa0154f0f6b4e4504497051872cf9148d2c7f54bf5315d08]
Error response from daemon: unable to remove volume: remove f36f3cb13883c61be4a3508b1ad788037e4a59a1fc78dc1955387ee57fa3760e: volume is in use - [0bcca8f7529dd55f5ad033c95a36950379f46ce91f4a9a7badd1882af813b15b]
The connection to the server 10.6.225.82:8443 was refused - did you specify the right host or port?
tput: unknown terminal "unknown"
E0625 15:00:34.013828    3782 start.go:297] Error starting cluster:  kubeadm init error
sudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests --ignore-preflight-errors=DirAvailable--data-minikube --ignore-preflight-errors=Port-10250 --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-etcd.yaml --ignore-preflight-errors=Swap --ignore-preflight-errors=CRI  &&
sudo /usr/bin/kubeadm alpha phase addon coredns
running command: : running command:
sudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests --ignore-preflight-errors=DirAvailable--data-minikube --ignore-preflight-errors=Port-10250 --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-etcd.yaml --ignore-preflight-errors=Swap --ignore-preflight-errors=CRI  &&
sudo /usr/bin/kubeadm alpha phase addon coredns

output: [init] Using Kubernetes version: v1.13.0
[preflight] Running pre-flight checks
        [WARNING SystemVerification]: this Docker version is not on the list of validated versions: 17.05.0-ce. Latest validated version: 18.06
        [WARNING Hostname]: hostname "minikube" could not be reached
        [WARNING Hostname]: hostname "minikube": lookup minikube on 149.156.4.11:53: no such host
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Activating the kubelet service
[certs] Using certificateDir folder "/var/lib/minikube/certs/"
[certs] Generating "front-proxy-ca" certificate and key
[certs] Generating "front-proxy-client" certificate and key
[certs] Generating "etcd/ca" certificate and key
[certs] Generating "apiserver-etcd-client" certificate and key
[certs] Generating "etcd/peer" certificate and key
[certs] etcd/peer serving cert is signed for DNS names [minikube localhost] and IPs [10.6.225.82 127.0.0.1 ::1]
[certs] Generating "etcd/healthcheck-client" certificate and key
[certs] Generating "etcd/server" certificate and key
[certs] etcd/server serving cert is signed for DNS names [minikube localhost] and IPs [10.6.225.82 127.0.0.1 ::1]
[certs] Using existing ca certificate authority
[certs] Using existing apiserver certificate and key on disk
[certs] Generating "apiserver-kubelet-client" certificate and key
[certs] Generating "sa" key and public key
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[kubeconfig] Using existing up-to-date kubeconfig file: "/etc/kubernetes/admin.conf"
[kubeconfig] Using existing up-to-date kubeconfig file: "/etc/kubernetes/kubelet.conf"
[kubeconfig] Using existing up-to-date kubeconfig file: "/etc/kubernetes/controller-manager.conf"
[kubeconfig] Using existing up-to-date kubeconfig file: "/etc/kubernetes/scheduler.conf"
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
[control-plane] Creating static Pod manifest for "kube-scheduler"
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[kubelet-check] Initial timeout of 40s passed.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused.

Unfortunately, an error has occurred:
        timed out waiting for the condition

This error is likely caused by:
        - The kubelet is not running
        - The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)

If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
        - 'systemctl status kubelet'
        - 'journalctl -xeu kubelet'

Additionally, a control plane component may have crashed or exited when started by the container runtime.
To troubleshoot, list all containers using your preferred container runtimes CLI, e.g. docker.
Here is one example how you may list all Kubernetes containers running in docker:
        - 'docker ps -a | grep kube | grep -v pause'
        Once you have found the failing container, you can inspect its logs with:
        - 'docker logs CONTAINERID'
error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster
: running command:
sudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests --ignore-preflight-errors=DirAvailable--data-minikube --ignore-preflight-errors=Port-10250 --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-etcd.yaml --ignore-preflight-errors=Swap --ignore-preflight-errors=CRI  &&
sudo /usr/bin/kubeadm alpha phase addon coredns

.: exit status 1
cp: cannot stat 'onedata/test-reports/*.xml': No such file or directory
ls: cannot access 'onedata/tests/gui/logs': No such file or directory
mv: cannot stat 'onedata/tests/gui/logs/report.*': No such file or directory
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  3103  100  3103    0     0   9606      0 --:--:-- --:--:-- --:--:--  9636
docker: Error response from daemon: grpc: the connection is unavailable.
time="2019-06-25T15:00:34+02:00" level=error msg="error getting events from daemon: net/http: request canceled"
Error: Get https://10.6.225.82:8443/api/v1/namespaces/kube-system/pods?labelSelector=app%3Dhelm%2Cname%3Dtiller: dial tcp 10.6.225.82:8443: connect: connection refused
The connection to the server 10.6.225.82:8443 was refused - did you specify the right host or port?
The connection to the server 10.6.225.82:8443 was refused - did you specify the right host or port?
The connection to the server 10.6.225.82:8443 was refused - did you specify the right host or port?
The connection to the server 10.6.225.82:8443 was refused - did you specify the right host or port?
The connection to the server 10.6.225.82:8443 was refused - did you specify the right host or port?
Error response from daemon: Cannot kill container 3bda9f9bb257: Container 3bda9f9bb257a36a1a5dc5a56ec391501e9dcfcfc9e5e6434d3ff1fb79c3c908 is not running
Error response from daemon: Cannot kill container 0bcca8f7529d: Cannot kill container 0bcca8f7529dd55f5ad033c95a36950379f46ce91f4a9a7badd1882af813b15b: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Could not kill running container 0bcca8f7529dd55f5ad033c95a36950379f46ce91f4a9a7badd1882af813b15b, cannot remove - Cannot kill container 0bcca8f7529dd55f5ad033c95a36950379f46ce91f4a9a7badd1882af813b15b: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Cannot kill container cf41be87de1a: Cannot kill container cf41be87de1abb2f260b7f4ef10cf6197a8f759a62ae151ed98c6ec81bdbfc68: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Could not kill running container cf41be87de1abb2f260b7f4ef10cf6197a8f759a62ae151ed98c6ec81bdbfc68, cannot remove - Cannot kill container cf41be87de1abb2f260b7f4ef10cf6197a8f759a62ae151ed98c6ec81bdbfc68: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Cannot kill container bebc3b3ec129: Cannot kill container bebc3b3ec129551e08ab91fefb7b055dae06ef2510f3a13a1644f0a68e88a957: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Could not kill running container bebc3b3ec129551e08ab91fefb7b055dae06ef2510f3a13a1644f0a68e88a957, cannot remove - Cannot kill container bebc3b3ec129551e08ab91fefb7b055dae06ef2510f3a13a1644f0a68e88a957: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Cannot kill container afbddad4467f: Cannot kill container afbddad4467f5267aa0154f0f6b4e4504497051872cf9148d2c7f54bf5315d08: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Could not kill running container afbddad4467f5267aa0154f0f6b4e4504497051872cf9148d2c7f54bf5315d08, cannot remove - Cannot kill container afbddad4467f5267aa0154f0f6b4e4504497051872cf9148d2c7f54bf5315d08: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Cannot kill container c7bebd9b7a4f: Cannot kill container c7bebd9b7a4f3b1292d31dd7b852b12b763f0df5ef2f9413b4b18e7cdf577a41: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Could not kill running container c7bebd9b7a4f3b1292d31dd7b852b12b763f0df5ef2f9413b4b18e7cdf577a41, cannot remove - Cannot kill container c7bebd9b7a4f3b1292d31dd7b852b12b763f0df5ef2f9413b4b18e7cdf577a41: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Cannot kill container 31bdc12941fa: Cannot kill container 31bdc12941fac77ec24fef819b798d53a66f9c85c771ca21a37df6a65709d006: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Could not kill running container 31bdc12941fac77ec24fef819b798d53a66f9c85c771ca21a37df6a65709d006, cannot remove - Cannot kill container 31bdc12941fac77ec24fef819b798d53a66f9c85c771ca21a37df6a65709d006: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Cannot kill container 9a84c52e5bcf: Cannot kill container 9a84c52e5bcf7d67e07fa2573a48330af8d4c9b11751bf56179684af5c91cb4a: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Could not kill running container 9a84c52e5bcf7d67e07fa2573a48330af8d4c9b11751bf56179684af5c91cb4a, cannot remove - Cannot kill container 9a84c52e5bcf7d67e07fa2573a48330af8d4c9b11751bf56179684af5c91cb4a: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Cannot kill container 48eeffce3bc9: Cannot kill container 48eeffce3bc974257408d0dac3663b7101115cb3d7450b7d09e9f44475b90b60: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Could not kill running container 48eeffce3bc974257408d0dac3663b7101115cb3d7450b7d09e9f44475b90b60, cannot remove - Cannot kill container 48eeffce3bc974257408d0dac3663b7101115cb3d7450b7d09e9f44475b90b60: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Cannot kill container 23fa860c5158: Cannot kill container 23fa860c51588263392b6496b0e66b44a12ef931255dd628d9c77c3c92129124: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Could not kill running container 23fa860c51588263392b6496b0e66b44a12ef931255dd628d9c77c3c92129124, cannot remove - Cannot kill container 23fa860c51588263392b6496b0e66b44a12ef931255dd628d9c77c3c92129124: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Cannot kill container b41447545dbe: Cannot kill container b41447545dbedd64f9bed289c6ba903a214b8b43de2f443553a0987f45f5625c: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Could not kill running container b41447545dbedd64f9bed289c6ba903a214b8b43de2f443553a0987f45f5625c, cannot remove - Cannot kill container b41447545dbedd64f9bed289c6ba903a214b8b43de2f443553a0987f45f5625c: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Cannot kill container fb2446ae2ca9: Cannot kill container fb2446ae2ca9105ae2889e7c62454065533a4657c2a1ff06a49b113632e5eb45: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Could not kill running container fb2446ae2ca9105ae2889e7c62454065533a4657c2a1ff06a49b113632e5eb45, cannot remove - Cannot kill container fb2446ae2ca9105ae2889e7c62454065533a4657c2a1ff06a49b113632e5eb45: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Cannot kill container 8d2c8afd0f9f: Cannot kill container 8d2c8afd0f9f29153a06c893cbdb0432214a5a0e15380223bb58a8bd4aa0074a: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Could not kill running container 8d2c8afd0f9f29153a06c893cbdb0432214a5a0e15380223bb58a8bd4aa0074a, cannot remove - Cannot kill container 8d2c8afd0f9f29153a06c893cbdb0432214a5a0e15380223bb58a8bd4aa0074a: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Cannot kill container b9ffe28e0acd: Cannot kill container b9ffe28e0acdc15285486253491b2d3221853c822a600802dfc6fe6c19f60c24: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Could not kill running container b9ffe28e0acdc15285486253491b2d3221853c822a600802dfc6fe6c19f60c24, cannot remove - Cannot kill container b9ffe28e0acdc15285486253491b2d3221853c822a600802dfc6fe6c19f60c24: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Cannot kill container db831e2086ab: Cannot kill container db831e2086abff4b5490283be8361a3716a33e2135bafc7ade06b6ae65f26f0b: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: Could not kill running container db831e2086abff4b5490283be8361a3716a33e2135bafc7ade06b6ae65f26f0b, cannot remove - Cannot kill container db831e2086abff4b5490283be8361a3716a33e2135bafc7ade06b6ae65f26f0b: rpc error: code = 14 desc = grpc: the connection is unavailable
Error response from daemon: unable to remove volume: remove 137c45e8754a844e25c66d419c67e6172070e9c6a6e916309294ab1a17ed6177: volume is in use - [afbddad4467f5267aa0154f0f6b4e4504497051872cf9148d2c7f54bf5315d08]
Error response from daemon: unable to remove volume: remove 1cba6fa3dcd34d5f422676927ac99c2447a7099df101ad4beb6379acd2e22f5e: volume is in use - [bebc3b3ec129551e08ab91fefb7b055dae06ef2510f3a13a1644f0a68e88a957]
Error response from daemon: unable to remove volume: remove 2f3274020e9dd83c0f8f926646337f21c7e3ffa1cc948869cac3e9a569fcb2a0: volume is in use - [48eeffce3bc974257408d0dac3663b7101115cb3d7450b7d09e9f44475b90b60]
Error response from daemon: unable to remove volume: remove 35de45e116fc02322e3145a2932e8a245f60a697845e75397f6b221c5967c077: volume is in use - [8d2c8afd0f9f29153a06c893cbdb0432214a5a0e15380223bb58a8bd4aa0074a]
Error response from daemon: unable to remove volume: remove 3aedc2b63acb146418dfabe0523cc919277e2e6b3d5c663a4597d41a3b3a6452: volume is in use - [fb2446ae2ca9105ae2889e7c62454065533a4657c2a1ff06a49b113632e5eb45]
Error response from daemon: unable to remove volume: remove 3dd7008c7991d747309ac69c9f1c5e6907c3b763e73a1a63b16c50cb7ff2426c: volume is in use - [b41447545dbedd64f9bed289c6ba903a214b8b43de2f443553a0987f45f5625c]
Error response from daemon: unable to remove volume: remove 53010c6640bab65f9bf1b3b085bb7c3a7376ad1faf4f622fdb2b057c56704668: volume is in use - [8d2c8afd0f9f29153a06c893cbdb0432214a5a0e15380223bb58a8bd4aa0074a]
Error response from daemon: unable to remove volume: remove 67e33d7d0bae815556903422081af560ce650d36d3c38d2603799bf53d714172: volume is in use - [c7bebd9b7a4f3b1292d31dd7b852b12b763f0df5ef2f9413b4b18e7cdf577a41]
Error response from daemon: unable to remove volume: remove 6bf08edc84a5423eb5963bca2dabda70c627f9c52a4ed13d1f2a6f46bd0d4b67: volume is in use - [cf41be87de1abb2f260b7f4ef10cf6197a8f759a62ae151ed98c6ec81bdbfc68]
Error response from daemon: unable to remove volume: remove 7256d970c7b4263d74c49e0e83240040c3fc2ae0d440f45ce1bbfc52bb9ea416: volume is in use - [48eeffce3bc974257408d0dac3663b7101115cb3d7450b7d09e9f44475b90b60]
Error response from daemon: unable to remove volume: remove 76596536d8441e1c5f19c66b02145d63a5b42826b0e75a3b37983b536ff6e779: volume is in use - [fb2446ae2ca9105ae2889e7c62454065533a4657c2a1ff06a49b113632e5eb45]
Error response from daemon: unable to remove volume: remove 9a6f603a33cd2a5afd89eb11b371fa4e7308e5fda34a0b1b19594943139b8639: volume is in use - [0bcca8f7529dd55f5ad033c95a36950379f46ce91f4a9a7badd1882af813b15b]
Error response from daemon: unable to remove volume: remove 9af68bada0f6615083e0ecfc122ed722290e68d8a536f27c97983acad38bcf31: volume is in use - [b41447545dbedd64f9bed289c6ba903a214b8b43de2f443553a0987f45f5625c]
Error response from daemon: unable to remove volume: remove 9d01be3708b29d781f41dba18019c06993e68df0bf2505592fd8506e67dad630: volume is in use - [cf41be87de1abb2f260b7f4ef10cf6197a8f759a62ae151ed98c6ec81bdbfc68]
Error response from daemon: unable to remove volume: remove a0d8814d71f31411bdba4c1b143ef255a516ceafd420221b134b61d70cffd945: volume is in use - [9a84c52e5bcf7d67e07fa2573a48330af8d4c9b11751bf56179684af5c91cb4a]
Error response from daemon: unable to remove volume: remove a6f3f84e9d543e2f5e34bd92ea85804240c2b2808bc32f10691f44abaab76706: volume is in use - [b9ffe28e0acdc15285486253491b2d3221853c822a600802dfc6fe6c19f60c24]
Error response from daemon: unable to remove volume: remove ace2eb2ee5bc2d1e02a4710a1d17b17e05d8a7d9fccaa9681cdb9348802ee83a: volume is in use - [31bdc12941fac77ec24fef819b798d53a66f9c85c771ca21a37df6a65709d006]
Error response from daemon: unable to remove volume: remove c1e5f066593d77594ca412ff7b23ac23e84bb4168d63b4730e7ab93d344f270e: volume is in use - [c7bebd9b7a4f3b1292d31dd7b852b12b763f0df5ef2f9413b4b18e7cdf577a41]
Error response from daemon: unable to remove volume: remove c27e21311dec910de623813e70500a3313c3401a72dbd67a051cf415446a2b1d: volume is in use - [9a84c52e5bcf7d67e07fa2573a48330af8d4c9b11751bf56179684af5c91cb4a]
Error response from daemon: unable to remove volume: remove d6770cd825883a029d1a76d32f81cb6a6b1f85832f5cff06188e7ab6c8e3407b: volume is in use - [db831e2086abff4b5490283be8361a3716a33e2135bafc7ade06b6ae65f26f0b]
Error response from daemon: unable to remove volume: remove d79f1baca87a3e525b1161e2386c4d423d699999487b49051d7a2597341f4f2b: volume is in use - [23fa860c51588263392b6496b0e66b44a12ef931255dd628d9c77c3c92129124]
Error response from daemon: unable to remove volume: remove daab064ec0c43f070488a95a526cb66426657ae69277691ee50b92336eb41f4e: volume is in use - [afbddad4467f5267aa0154f0f6b4e4504497051872cf9148d2c7f54bf5315d08]
Error response from daemon: unable to remove volume: remove f36f3cb13883c61be4a3508b1ad788037e4a59a1fc78dc1955387ee57fa3760e: volume is in use - [0bcca8f7529dd55f5ad033c95a36950379f46ce91f4a9a7badd1882af813b15b]