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.

Sign up for GitHub

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

Jump to bottom

The Secrets Store CSI Driver installation fails on minikube #49

Closed
ryysud opened this issue Aug 8, 2019 · 11 comments
Closed

The Secrets Store CSI Driver installation fails on minikube #49

ryysud opened this issue Aug 8, 2019 · 11 comments
Labels
documentation kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@ryysud
Copy link
Contributor

ryysud commented Aug 8, 2019 •
edited
Loading

I tried to run "HashiCorp Vault Provider for Secret Store CSI Driver" on minikube according to the guide.

1. Start kubernetes cluster (v1.15.2) using minikube.

$ minikube start --feature-gates=CSIInlineVolume=true

Versions of minikube and docker are below.

$ minikube version: v1.3.0
commit: 43969594266d77b555a207b0f3e9b3fa1dc92b1f

$ docker version
Client: Docker Engine - Community
 Version:           19.03.1
 API version:       1.40
 Go version:        go1.12.5
 Git commit:        74b1e89
 Built:             Thu Jul 25 21:18:17 2019
 OS/Arch:           darwin/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.1
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.5
  Git commit:       74b1e89
  Built:            Thu Jul 25 21:17:52 2019
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.2.6
  GitCommit:        894b81a4b802e4eb2a91d1ce216b8817763c29fb
 runc:
  Version:          1.0.0-rc8
  GitCommit:        425e105d5a03fabd737a126ad93d62a9eeede87f
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

2. Set up a vault cluster

I created a development HashiCorp Vault cluster in Kubernetes according to the following guide.
https://github.com/deislabs/secrets-store-csi-driver/blob/master/pkg/providers/vault/docs/vault-setup.md

3. Install the Secrets Store CSI Driver

I installed the Secrets Store CSI Driver according to the following guide.
https://github.com/deislabs/secrets-store-csi-driver/tree/master/pkg/providers/vault#install-the-secrets-store-csi-driver-kubernetes-version-115x

But creating the anubhavmishra/secrets-store-csi:v0.0.3 container failed.

$ kubectl apply -f pkg/providers/vault/examples/secrets-store-csi-driver.yaml

$ kubectl get po
NAME                           READY   STATUS              RESTARTS   AGE
csi-secrets-store-7gdsh        1/2     RunContainerError   0          47m
csi-secrets-store-attacher-0   1/1     Running             0          47m
vault-6df55d6866-js8zc         1/1     Running             0          54m

$ kubectl describe pod csi-secrets-store-7gdsh
...
Events:
  Type     Reason     Age   From               Message
  ----     ------     ----  ----               -------
  Normal   Scheduled  48m   default-scheduler  Successfully assigned default/csi-secrets-store-7gdsh to minikube
  Normal   Pulling    48m   kubelet, minikube  Pulling image "gcr.io/gke-release/csi-driver-registrar:v1.0.1-gke.0"
  Normal   Pulled     48m   kubelet, minikube  Successfully pulled image "gcr.io/gke-release/csi-driver-registrar:v1.0.1-gke.0"
  Normal   Created    48m   kubelet, minikube  Created container driver-registrar
  Normal   Started    48m   kubelet, minikube  Started container driver-registrar
  Normal   Pulling    48m   kubelet, minikube  Pulling image "anubhavmishra/secrets-store-csi:v0.0.3"
  Normal   Pulled     48m   kubelet, minikube  Successfully pulled image "anubhavmishra/secrets-store-csi:v0.0.3"
  Normal   Created    48m   kubelet, minikube  Created container secrets-store
  Warning  Failed     48m   kubelet, minikube  Error: failed to start container "secrets-store": Error response from daemon: OCI runtime create failed: open /var/run/docker/runtime-runc/moby/secrets-store/state.json: no such file or directory: unknown

How can I resolve this problem...?
@ryysud
Copy link
Contributor Author

ryysud commented Aug 9, 2019

I tried to resolve it with the following changes, but it failed as well.

$ git diff
diff --git a/deploy/csi-secrets-store-attacher.yaml b/deploy/csi-secrets-store-attacher.yaml
index 126123b9..1a3636e7 100644
--- a/deploy/csi-secrets-store-attacher.yaml
+++ b/deploy/csi-secrets-store-attacher.yaml
@@ -30,7 +30,7 @@ spec:
       serviceAccountName: csi-attacher
       containers:
         - name: csi-attacher
-          image: gcr.io/gke-release/csi-attacher:v1.0.0-gke.0
+          image: quay.io/k8scsi/csi-attacher:v1.2.0
           args:
             - --v=5
             - --csi-address=$(ADDRESS)
diff --git a/pkg/providers/vault/examples/secrets-store-csi-driver.yaml b/pkg/providers/vault/examples/secrets-store-csi-driver.yaml
index d92652fd..8402795b 100644
--- a/pkg/providers/vault/examples/secrets-store-csi-driver.yaml
+++ b/pkg/providers/vault/examples/secrets-store-csi-driver.yaml
@@ -15,7 +15,7 @@ spec:
       hostNetwork: true
       containers:
         - name: driver-registrar
-          image: gcr.io/gke-release/csi-driver-registrar:v1.0.1-gke.0
+          image: quay.io/k8scsi/csi-node-driver-registrar:v1.1.0
           args:
             - --v=5
             - --csi-address=/csi/csi.sock
@@ -33,7 +33,7 @@ spec:
           - mountPath: /registration
             name: registration-dir
         - name: secrets-store
-          image: anubhavmishra/secrets-store-csi:v0.0.3
+          image: ritazh/secrets-store-csi:v0.0.4
           args:
             - "--v=5"
             - "--endpoint=$(CSI_ENDPOINT)"

@ryysud
Copy link
Contributor Author

ryysud commented Aug 9, 2019 •
edited
Loading

This issue seems to be related to kubernetes/minikube#4072 and kubernetes/minikube#3512 (comment) .

$ minikube logs
==> kubelet <==
-- Logs begin at Fri 2019-08-09 07:43:41 UTC, end at Fri 2019-08-09 07:55:42 UTC. --
Aug 09 07:55:12 minikube kubelet[3418]: E0809 07:55:12.856700    3418 remote_runtime.go:351] ExecSync 32545d4d9575398f43b7bba3da2a0e30ff57ce136ac6760454f3c292d5ead599 '/bin/sh -ec ETCDCTL_API=3 etcdctl --endpoints=https://[127.0.0.1]:2379 --cacert=/var/lib/minikube/certs//etcd/ca.crt --cert=/var/lib/minikube/certs//etcd/healthcheck-client.crt --key=/var/lib/minikube/certs//etcd/healthcheck-client.key get foo' from runtime service failed: rpc error: code = Unknown desc = cannot connect to the Docker daemon. Is 'docker daemon' running on this host?: dial unix /var/run/docker.sock: connect: no such file or directory
Aug 09 07:55:12 minikube kubelet[3418]: E0809 07:55:12.858075    3418 remote_runtime.go:351] ExecSync 32545d4d9575398f43b7bba3da2a0e30ff57ce136ac6760454f3c292d5ead599 '/bin/sh -ec ETCDCTL_API=3 etcdctl --endpoints=https://[127.0.0.1]:2379 --cacert=/var/lib/minikube/certs//etcd/ca.crt --cert=/var/lib/minikube/certs//etcd/healthcheck-client.crt --key=/var/lib/minikube/certs//etcd/healthcheck-client.key get foo' from runtime service failed: rpc error: code = Unknown desc = cannot connect to the Docker daemon. Is 'docker daemon' running on this host?: dial unix /var/run/docker.sock: connect: no such file or directory
Aug 09 07:55:20 minikube kubelet[3418]: E0809 07:55:20.756639    3418 kuberuntime_manager.go:729] GeneratePodSandboxConfig for pod "nginx-ingress-controller-5d9cf9c69f-wbctz_kube-system(b1c083dc-8337-429c-8832-9f1d1fc6e20a)" failed: open /etc/resolv.conf: no such file or directory
Aug 09 07:55:20 minikube kubelet[3418]: E0809 07:55:20.757309    3418 pod_workers.go:190] Error syncing pod b1c083dc-8337-429c-8832-9f1d1fc6e20a ("nginx-ingress-controller-5d9cf9c69f-wbctz_kube-system(b1c083dc-8337-429c-8832-9f1d1fc6e20a)"), skipping: failed to "ConfigPodSandbox" for "e2184812098df18ce31c3a2443fd366ea80ef7c0be75e8e4934d6140b41911af" with ConfigPodSandboxError: "GeneratePodSandboxConfig for pod \"nginx-ingress-controller-5d9cf9c69f-wbctz_kube-system(b1c083dc-8337-429c-8832-9f1d1fc6e20a)\" failed: open /etc/resolv.conf: no such file or directory"
Aug 09 07:55:20 minikube kubelet[3418]: E0809 07:55:20.757614    3418 kuberuntime_manager.go:729] GeneratePodSandboxConfig for pod "coredns-5c98db65d4-jbks4_kube-system(a9932c7c-53b9-484c-ad5f-7ea7a01c4f0c)" failed: open /etc/resolv.conf: no such file or directory
Aug 09 07:55:20 minikube kubelet[3418]: E0809 07:55:20.757993    3418 pod_workers.go:190] Error syncing pod a9932c7c-53b9-484c-ad5f-7ea7a01c4f0c ("coredns-5c98db65d4-jbks4_kube-system(a9932c7c-53b9-484c-ad5f-7ea7a01c4f0c)"), skipping: failed to "ConfigPodSandbox" for "aca5712cfebc1c9ac7b59a0877cf59e2f84b3ceb20d3392fc5340fde2bc2e6e0" with ConfigPodSandboxError: "GeneratePodSandboxConfig for pod \"coredns-5c98db65d4-jbks4_kube-system(a9932c7c-53b9-484c-ad5f-7ea7a01c4f0c)\" failed: open /etc/resolv.conf: no such file or directory"
Aug 09 07:55:20 minikube kubelet[3418]: E0809 07:55:20.757073    3418 kuberuntime_manager.go:729] GeneratePodSandboxConfig for pod "csi-secrets-store-lxjzs_default(3d7bcd8d-ca5e-4fba-8b21-0083c188b7a6)" failed: open /etc/resolv.conf: no such file or directory
Aug 09 07:55:20 minikube kubelet[3418]: E0809 07:55:20.758016    3418 pod_workers.go:190] Error syncing pod 3d7bcd8d-ca5e-4fba-8b21-0083c188b7a6 ("csi-secrets-store-lxjzs_default(3d7bcd8d-ca5e-4fba-8b21-0083c188b7a6)"), skipping: failed to "ConfigPodSandbox" for "26108a13468f81b0bb9d100eb12c68aab59dea3f54e8c156cbd311550cf8833f" with ConfigPodSandboxError: "GeneratePodSandboxConfig for pod \"csi-secrets-store-lxjzs_default(3d7bcd8d-ca5e-4fba-8b21-0083c188b7a6)\" failed: open /etc/resolv.conf: no such file or directory"
Aug 09 07:55:20 minikube kubelet[3418]: E0809 07:55:20.757846    3418 kuberuntime_manager.go:729] GeneratePodSandboxConfig for pod "etcd-minikube_kube-system(93e1856cbfcd056e4d1aa4cca94fae53)" failed: open /etc/resolv.conf: no such file or directory
Aug 09 07:55:20 minikube kubelet[3418]: E0809 07:55:20.758035    3418 pod_workers.go:190] Error syncing pod 93e1856cbfcd056e4d1aa4cca94fae53 ("etcd-minikube_kube-system(93e1856cbfcd056e4d1aa4cca94fae53)"), skipping: failed to "ConfigPodSandbox" for "0f0d2aa0f11fc748f53a3930bd4c199f12ec39919177a6eeea3a615c2874b689" with ConfigPodSandboxError: "GeneratePodSandboxConfig for pod \"etcd-minikube_kube-system(93e1856cbfcd056e4d1aa4cca94fae53)\" failed: open /etc/resolv.conf: no such file or directory"
Aug 09 07:55:20 minikube kubelet[3418]: E0809 07:55:20.756668    3418 kuberuntime_manager.go:729] GeneratePodSandboxConfig for pod "vault-6df55d6866-rwx8p_default(a8244b83-4388-4ea3-b7eb-73a2a0f6a585)" failed: open /etc/resolv.conf: no such file or directory
Aug 09 07:55:20 minikube kubelet[3418]: E0809 07:55:20.758055    3418 pod_workers.go:190] Error syncing pod a8244b83-4388-4ea3-b7eb-73a2a0f6a585 ("vault-6df55d6866-rwx8p_default(a8244b83-4388-4ea3-b7eb-73a2a0f6a585)"), skipping: failed to "ConfigPodSandbox" for "f47deb50a8b505da161dd61d8c3573ee963838dca1368953e3fc3602b48f8cd8" with ConfigPodSandboxError: "GeneratePodSandboxConfig for pod \"vault-6df55d6866-rwx8p_default(a8244b83-4388-4ea3-b7eb-73a2a0f6a585)\" failed: open /etc/resolv.conf: no such file or directory"
Aug 09 07:55:22 minikube kubelet[3418]: E0809 07:55:22.852042    3418 remote_runtime.go:351] ExecSync 32545d4d9575398f43b7bba3da2a0e30ff57ce136ac6760454f3c292d5ead599 '/bin/sh -ec ETCDCTL_API=3 etcdctl --endpoints=https://[127.0.0.1]:2379 --cacert=/var/lib/minikube/certs//etcd/ca.crt --cert=/var/lib/minikube/certs//etcd/healthcheck-client.crt --key=/var/lib/minikube/certs//etcd/healthcheck-client.key get foo' from runtime service failed: rpc error: code = Unknown desc = cannot connect to the Docker daemon. Is 'docker daemon' running on this host?: dial unix /var/run/docker.sock: connect: no such file or directory
Aug 09 07:55:22 minikube kubelet[3418]: E0809 07:55:22.853019    3418 remote_runtime.go:351] ExecSync 32545d4d9575398f43b7bba3da2a0e30ff57ce136ac6760454f3c292d5ead599 '/bin/sh -ec ETCDCTL_API=3 etcdctl --endpoints=https://[127.0.0.1]:2379 --cacert=/var/lib/minikube/certs//etcd/ca.crt --cert=/var/lib/minikube/certs//etcd/healthcheck-client.crt --key=/var/lib/minikube/certs//etcd/healthcheck-client.key get foo' from runtime service failed: rpc error: code = Unknown desc = cannot connect to the Docker daemon. Is 'docker daemon' running on this host?: dial unix /var/run/docker.sock: connect: no such file or directory
Aug 09 07:55:22 minikube kubelet[3418]: E0809 07:55:22.853993    3418 remote_runtime.go:351] ExecSync 32545d4d9575398f43b7bba3da2a0e30ff57ce136ac6760454f3c292d5ead599 '/bin/sh -ec ETCDCTL_API=3 etcdctl --endpoints=https://[127.0.0.1]:2379 --cacert=/var/lib/minikube/certs//etcd/ca.crt --cert=/var/lib/minikube/certs//etcd/healthcheck-client.crt --key=/var/lib/minikube/certs//etcd/healthcheck-client.key get foo' from runtime service failed: rpc error: code = Unknown desc = cannot connect to the Docker daemon. Is 'docker daemon' running on this host?: dial unix /var/run/docker.sock: connect: no such file or directory
Aug 09 07:55:31 minikube kubelet[3418]: E0809 07:55:31.756353    3418 kuberuntime_manager.go:729] GeneratePodSandboxConfig for pod "coredns-5c98db65d4-jbks4_kube-system(a9932c7c-53b9-484c-ad5f-7ea7a01c4f0c)" failed: open /etc/resolv.conf: no such file or directory
Aug 09 07:55:31 minikube kubelet[3418]: E0809 07:55:31.756498    3418 pod_workers.go:190] Error syncing pod a9932c7c-53b9-484c-ad5f-7ea7a01c4f0c ("coredns-5c98db65d4-jbks4_kube-system(a9932c7c-53b9-484c-ad5f-7ea7a01c4f0c)"), skipping: failed to "ConfigPodSandbox" for "aca5712cfebc1c9ac7b59a0877cf59e2f84b3ceb20d3392fc5340fde2bc2e6e0" with ConfigPodSandboxError: "GeneratePodSandboxConfig for pod \"coredns-5c98db65d4-jbks4_kube-system(a9932c7c-53b9-484c-ad5f-7ea7a01c4f0c)\" failed: open /etc/resolv.conf: no such file or directory"
Aug 09 07:55:31 minikube kubelet[3418]: E0809 07:55:31.756993    3418 kuberuntime_manager.go:729] GeneratePodSandboxConfig for pod "etcd-minikube_kube-system(93e1856cbfcd056e4d1aa4cca94fae53)" failed: open /etc/resolv.conf: no such file or directory
Aug 09 07:55:31 minikube kubelet[3418]: E0809 07:55:31.757022    3418 pod_workers.go:190] Error syncing pod 93e1856cbfcd056e4d1aa4cca94fae53 ("etcd-minikube_kube-system(93e1856cbfcd056e4d1aa4cca94fae53)"), skipping: failed to "ConfigPodSandbox" for "0f0d2aa0f11fc748f53a3930bd4c199f12ec39919177a6eeea3a615c2874b689" with ConfigPodSandboxError: "GeneratePodSandboxConfig for pod \"etcd-minikube_kube-system(93e1856cbfcd056e4d1aa4cca94fae53)\" failed: open /etc/resolv.conf: no such file or directory"
Aug 09 07:55:32 minikube kubelet[3418]: E0809 07:55:32.851635    3418 remote_runtime.go:351] ExecSync 32545d4d9575398f43b7bba3da2a0e30ff57ce136ac6760454f3c292d5ead599 '/bin/sh -ec ETCDCTL_API=3 etcdctl --endpoints=https://[127.0.0.1]:2379 --cacert=/var/lib/minikube/certs//etcd/ca.crt --cert=/var/lib/minikube/certs//etcd/healthcheck-client.crt --key=/var/lib/minikube/certs//etcd/healthcheck-client.key get foo' from runtime service failed: rpc error: code = Unknown desc = cannot connect to the Docker daemon. Is 'docker daemon' running on this host?: dial unix /var/run/docker.sock: connect: no such file or directory
Aug 09 07:55:32 minikube kubelet[3418]: E0809 07:55:32.854154    3418 remote_runtime.go:351] ExecSync 32545d4d9575398f43b7bba3da2a0e30ff57ce136ac6760454f3c292d5ead599 '/bin/sh -ec ETCDCTL_API=3 etcdctl --endpoints=https://[127.0.0.1]:2379 --cacert=/var/lib/minikube/certs//etcd/ca.crt --cert=/var/lib/minikube/certs//etcd/healthcheck-client.crt --key=/var/lib/minikube/certs//etcd/healthcheck-client.key get foo' from runtime service failed: rpc error: code = Unknown desc = cannot connect to the Docker daemon. Is 'docker daemon' running on this host?: dial unix /var/run/docker.sock: connect: no such file or directory
Aug 09 07:55:32 minikube kubelet[3418]: E0809 07:55:32.858075    3418 remote_runtime.go:351] ExecSync 32545d4d9575398f43b7bba3da2a0e30ff57ce136ac6760454f3c292d5ead599 '/bin/sh -ec ETCDCTL_API=3 etcdctl --endpoints=https://[127.0.0.1]:2379 --cacert=/var/lib/minikube/certs//etcd/ca.crt --cert=/var/lib/minikube/certs//etcd/healthcheck-client.crt --key=/var/lib/minikube/certs//etcd/healthcheck-client.key get foo' from runtime service failed: rpc error: code = Unknown desc = cannot connect to the Docker daemon. Is 'docker daemon' running on this host?: dial unix /var/run/docker.sock: connect: no such file or directory
Aug 09 07:55:33 minikube kubelet[3418]: E0809 07:55:33.756028    3418 kuberuntime_manager.go:729] GeneratePodSandboxConfig for pod "vault-6df55d6866-rwx8p_default(a8244b83-4388-4ea3-b7eb-73a2a0f6a585)" failed: open /etc/resolv.conf: no such file or directory
Aug 09 07:55:33 minikube kubelet[3418]: E0809 07:55:33.756086    3418 pod_workers.go:190] Error syncing pod a8244b83-4388-4ea3-b7eb-73a2a0f6a585 ("vault-6df55d6866-rwx8p_default(a8244b83-4388-4ea3-b7eb-73a2a0f6a585)"), skipping: failed to "ConfigPodSandbox" for "f47deb50a8b505da161dd61d8c3573ee963838dca1368953e3fc3602b48f8cd8" with ConfigPodSandboxError: "GeneratePodSandboxConfig for pod \"vault-6df55d6866-rwx8p_default(a8244b83-4388-4ea3-b7eb-73a2a0f6a585)\" failed: open /etc/resolv.conf: no such file or directory"
Aug 09 07:55:33 minikube kubelet[3418]: E0809 07:55:33.756571    3418 kuberuntime_manager.go:729] GeneratePodSandboxConfig for pod "nginx-ingress-controller-5d9cf9c69f-wbctz_kube-system(b1c083dc-8337-429c-8832-9f1d1fc6e20a)" failed: open /etc/resolv.conf: no such file or directory
Aug 09 07:55:33 minikube kubelet[3418]: E0809 07:55:33.756611    3418 pod_workers.go:190] Error syncing pod b1c083dc-8337-429c-8832-9f1d1fc6e20a ("nginx-ingress-controller-5d9cf9c69f-wbctz_kube-system(b1c083dc-8337-429c-8832-9f1d1fc6e20a)"), skipping: failed to "ConfigPodSandbox" for "e2184812098df18ce31c3a2443fd366ea80ef7c0be75e8e4934d6140b41911af" with ConfigPodSandboxError: "GeneratePodSandboxConfig for pod \"nginx-ingress-controller-5d9cf9c69f-wbctz_kube-system(b1c083dc-8337-429c-8832-9f1d1fc6e20a)\" failed: open /etc/resolv.conf: no such file or directory"
Aug 09 07:55:35 minikube kubelet[3418]: E0809 07:55:35.756371    3418 kuberuntime_manager.go:729] GeneratePodSandboxConfig for pod "csi-secrets-store-lxjzs_default(3d7bcd8d-ca5e-4fba-8b21-0083c188b7a6)" failed: open /etc/resolv.conf: no such file or directory
Aug 09 07:55:35 minikube kubelet[3418]: E0809 07:55:35.756872    3418 pod_workers.go:190] Error syncing pod 3d7bcd8d-ca5e-4fba-8b21-0083c188b7a6 ("csi-secrets-store-lxjzs_default(3d7bcd8d-ca5e-4fba-8b21-0083c188b7a6)"), skipping: failed to "ConfigPodSandbox" for "26108a13468f81b0bb9d100eb12c68aab59dea3f54e8c156cbd311550cf8833f" with ConfigPodSandboxError: "GeneratePodSandboxConfig for pod \"csi-secrets-store-lxjzs_default(3d7bcd8d-ca5e-4fba-8b21-0083c188b7a6)\" failed: open /etc/resolv.conf: no such file or directory"
Aug 09 07:55:40 minikube kubelet[3418]: E0809 07:55:40.756541    3418 kuberuntime_manager.go:729] GeneratePodSandboxConfig for pod "kube-apiserver-minikube_kube-system(51d9d2220f4d2efeed22480bc518750d)" failed: open /etc/resolv.conf: no such file or directory
Aug 09 07:55:40 minikube kubelet[3418]: E0809 07:55:40.757463    3418 pod_workers.go:190] Error syncing pod 51d9d2220f4d2efeed22480bc518750d ("kube-apiserver-minikube_kube-system(51d9d2220f4d2efeed22480bc518750d)"), skipping: failed to "ConfigPodSandbox" for "51a51912d043d83a6aec5a40420bd5467a1d95ec36707b86f35cdcf8a5c62ba4" with ConfigPodSandboxError: "GeneratePodSandboxConfig for pod \"kube-apiserver-minikube_kube-system(51d9d2220f4d2efeed22480bc518750d)\" failed: open /etc/resolv.conf: no such file or directory"

💣  Error getting machine logs: unable to fetch logs for: container status

😿  Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
👉  https://github.com/kubernetes/minikube/issues/new/choose

$ minikube ssh -- cat /etc/resolv.conf
cat: /etc/resolv.conf: No such file or directory
ssh: Process exited with status 1

@ryysud ryysud mentioned this issue Aug 9, 2019
Closed
@ritazh
Copy link
Member

ritazh commented Aug 9, 2019

Thank you for reporting this issue and the investigation. We will look into this as well.

@ritazh ritazh added kind/bug Categorizes issue or PR as related to a bug. documentation labels Dec 12, 2019
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 11, 2020
@aramase
Copy link
Member

aramase commented Mar 11, 2020

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 11, 2020
@ritazh
Copy link
Member

ritazh commented Apr 8, 2020

/assign @helayoty

@k8s-ci-robot
Copy link
Contributor

@ritazh: GitHub didn't allow me to assign the following users: helayoty.

Note that only kubernetes-sigs members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @helayoty

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@helayoty
Copy link
Contributor

helayoty commented Apr 9, 2020 •
edited
Loading

Hi @ryysud , Thank you for the well-detailed issue. We have been able to reproduce the issue and it seems it's a minikube issue, not something specific to the secrets-store csi driver project. You can try KIND instead.

Please let us know if you have further questions!

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 8, 2020
@aramase
Copy link
Member

aramase commented Jul 16, 2020

/close

Closing this issue as it's a known problem with minikube. Please feel free to reopen if you're having issues trying the driver with KIND clusters.

@k8s-ci-robot
Copy link
Contributor

@aramase: Closing this issue.

In response to this:

/close

Closing this issue as it's a known problem with minikube. Please feel free to reopen if you're having issues trying the driver with KIND clusters.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
documentation kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@ritazh @ryysud @aramase @k8s-ci-robot @fejta-bot @helayoty