You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// make sure the order of apply. `csi-hostpath-snapshotclass` must be the first position, because it depends on `snapshot.storage.k8s.io_volumesnapshotclasses`
Copy file name to clipboardExpand all lines: pkg/minikube/config/types.go
+1-1
Original file line number
Diff line number
Diff line change
@@ -76,7 +76,7 @@ type ClusterConfig struct {
76
76
KubernetesConfigKubernetesConfig
77
77
Nodes []Node
78
78
Addonsmap[string]bool
79
-
CustomAddonImagesmap[string]string// Maps image names to the image to use for addons. e.g. Dashboard -> k8s.gcr.io/echoserver:1.4 makes dashboard addon use echoserver for its Dashboard deployment.
79
+
CustomAddonImagesmap[string]string// Maps image names to the image to use for addons. e.g. Dashboard -> registry.k8s.io/echoserver:1.4 makes dashboard addon use echoserver for its Dashboard deployment.
80
80
CustomAddonRegistriesmap[string]string// Maps image names to the registry to use for addons. See CustomAddonImages for example.
81
81
VerifyComponentsmap[string]bool// map of components to verify and wait for after start.
{4913, "linux", "PR_KVM_CREATE_BUSY", `Unable to start VM: create: Error creating machine: Error in driver during machine creation: error creating VM: virError(Code=1, Domain=10, Message='internal error: process exited while connecting to monitor: ioctl(KVM_CREATE_VM) failed: 16 Device or resource busy`},
54
54
{5950, "linux", "PR_KVM_ISO_PERMISSION", `Retriable failure: create: Error creating machine: Error in driver during machine creation: error creating VM: virError(Code=1, Domain=10, Message='internal error: qemu unexpectedly closed the monitor: 2019-11-19T16:08:16.757609Z qemu-kvm: -drive file=/home/lnicotra/.minikube/machines/minikube/boot2docker.iso,format=raw,if=none,id=drive-scsi0-0-0-2,readonly=on: could not open disk image /home/lnicotra/.minikube/machines/minikube/boot2docker.iso: Could not open '/home/lnicotra/.minikube/machines/minikube/boot2docker.iso': Permission denied'`},
55
55
{5836, "", "SVC_OPEN_NOT_FOUND", `Error opening service: Service kubernetes-bootcamp was not found in "default" namespace. You may select another namespace by using 'minikube service kubernetes-bootcamp -n : Temporary Error: Error getting service kubernetes-bootcamp: services "kubernetes-bootcamp" not found`},
56
-
{3898, "", "INET_PULL_TIMEOUT", `[ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-controller-manager:v1.17.0: output: Error response from daemon: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)`},
56
+
{3898, "", "INET_PULL_TIMEOUT", `[ERROR ImagePull]: failed to pull image registry.k8s.io/kube-controller-manager:v1.17.0: output: Error response from daemon: Get https://registry.k8s.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)`},
57
57
{6079, "darwin", "PR_HYPERKIT_CRASHED", `Error creating machine: Error in driver during machine creation: hyperkit crashed! command line:`},
58
58
{5636, "linux", "INET_DEFAULT_ROUTE", `Unable to get VM IP address: unable to select an IP from default routes.`},
59
59
{6087, "", "GUEST_DOES_NOT_EXIST", `Error getting host status: state: machine does not exist`},
Copy file name to clipboardExpand all lines: site/content/en/docs/handbook/vpn_and_proxy.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -72,8 +72,8 @@ This error indicates that the host:port combination defined by HTTPS_PROXY or HT
72
72
```text
73
73
Unable to pull images, which may be OK:
74
74
75
-
failed to pull image "k8s.gcr.io/kube-apiserver:v1.13.3": output: Error response from daemon:
76
-
Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection
75
+
failed to pull image "registry.k8s.io/kube-apiserver:v1.13.3": output: Error response from daemon:
76
+
Get https://registry.k8s.io/v2/: net/http: request canceled while waiting for connection
77
77
(Client.Timeout exceeded while awaiting headers)
78
78
```
79
79
@@ -82,9 +82,9 @@ This error indicates that the container runtime running within the VM does not h
82
82
#### x509: certificate signed by unknown authority
83
83
84
84
```text
85
-
[ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-apiserver:v1.13.3:
85
+
[ERROR ImagePull]: failed to pull image registry.k8s.io/kube-apiserver:v1.13.3:
86
86
output: Error response from daemon:
87
-
Get https://k8s.gcr.io/v2/: x509: certificate signed by unknown authority
87
+
Get https://registry.k8s.io/v2/: x509: certificate signed by unknown authority
88
88
```
89
89
90
90
This is because minikube VM is stuck behind a proxy that rewrites HTTPS responses to contain its own TLS certificate. The [solution](https://github.com/kubernetes/minikube/issues/3613#issuecomment-461034222) is to install the proxy certificate into a location that is copied to the VM at startup, so that it can be validated.
0 commit comments