broke down GUEST_START error code

pull/11529/head
Steven Powell 2021-05-27 14:42:52 -07:00
parent 7ee9c6df69
commit 5be0d5fe9f
9 changed files with 67 additions and 0 deletions

View File

@ -267,6 +267,15 @@ var providerIssues = []match{
GOOS: []string{"windows"},
Regexp: re(`docker:.*Mounts denied: EOF`),
},
{
Kind: Kind{
ID: "PR_DOCKER_UNSUPPORTED",
ExitCode: ExProviderError,
Advice: "Update Docker to the latest minor version, this version is unsupported",
Issues: []int{10362},
},
Regexp: re(`unexpected "=" in operand`),
},
// Hyperkit hypervisor
{
@ -997,6 +1006,32 @@ var guestIssues = []match{
},
Regexp: re(`'/var/lib/dpkg': No such file or directory`),
},
{
Kind: Kind{
ID: "GUEST_INCORRECT_ARCH",
ExitCode: ExGuestUnsupported,
Advice: "You might be using an amd64 version of minikube on a M1 Mac, use the arm64 version of minikube instead",
Issues: []int{10243},
},
Regexp: re(`qemu: uncaught target signal 11 (Segmentation fault) - core dumped`),
},
{
Kind: Kind{
ID: "GUEST_CERTS_EXPIRED",
ExitCode: ExGuestError,
Advice: "Your minikube certs likely expired, as a workaround, clear your minikube home dir `minikube delete --all --purge`",
Issues: []int{10948},
},
Regexp: re(`controlPlane never updated to`),
},
{
Kind: Kind{
ID: "GUEST_CNI_INCOMPATIBLE",
ExitCode: ExGuestUnsupported,
Advice: "Bridge CNI is incompatible with multi-node clusters, use a different CNI",
},
Regexp: re(`bridge CNI is incompatible with multi-node clusters`),
},
{
Kind: Kind{
ID: "GUEST_PROVISION_ACQUIRE_LOCK",

View File

@ -66,6 +66,7 @@
"Bind Address: {{.Address}}": "",
"Booting up control plane ...": "",
"Both driver={{.driver}} and vm-driver={{.vmd}} have been set.\n\n Since vm-driver is deprecated, minikube will default to driver={{.driver}}.\n\n If vm-driver is set in the global config, please run \"minikube config unset vm-driver\" to resolve this warning.\n\t\t\t": "",
"Bridge CNI is incompatible with multi-node clusters, use a different CNI": "",
"Build a container image in minikube": "",
"Build a container image, using the container runtime.": "",
"CNI plug-in to use. Valid options: auto, bridge, calico, cilium, flannel, kindnet, or path to a CNI manifest (default: auto)": "",
@ -731,6 +732,7 @@
"Unpausing node {{.name}} ... ": "",
"Unset the KUBECONFIG environment variable, or verify that it does not point to an empty or otherwise invalid path": "",
"Unset variables instead of setting them": "",
"Update Docker to the latest minor version, this version is unsupported": "",
"Update kubeconfig in case of an IP or port change": "",
"Update server returned an empty list": "",
"Updating the running {{.driver_name}} \"{{.cluster}}\" {{.machine_type}} ...": "",
@ -797,12 +799,14 @@
"You have chosen to disable the CNI but the \\\"{{.name}}\\\" container runtime requires CNI": "",
"You may need to manually remove the \"{{.name}}\" VM from your hypervisor": "Möglicherweise müssen Sie die VM \"{{.name}}\" manuell von Ihrem Hypervisor entfernen",
"You may need to stop the Hyper-V Manager and run `minikube delete` again.": "",
"You might be using an amd64 version of minikube on a M1 Mac, use the arm64 version of minikube instead": "",
"You must specify a service name": "",
"Your GCP credentials will now be mounted into every pod created in the {{.name}} cluster.": "",
"Your cgroup does not allow setting memory.": "",
"Your host does not support KVM virtualization. Ensure that qemu-kvm is installed, and run 'virt-host-validate' to debug the problem": "",
"Your host does not support virtualization. If you are running minikube within a VM, try '--driver=docker'. Otherwise, enable virtualization in your BIOS": "",
"Your host is failing to route packets to the minikube VM. If you have VPN software, try turning it off or configuring it so that it does not re-route traffic to the VM IP. If not, check your VM environment routing options.": "",
"Your minikube certs likely expired, as a workaround, clear your minikube home dir `minikube delete --all --purge`": "",
"Your minikube config refers to an unsupported driver. Erase ~/.minikube, and try again.": "",
"Your minikube vm is not running, try minikube start.": "",
"[WARNING] For full functionality, the 'csi-hostpath-driver' addon requires the 'volumesnapshots' addon to be enabled.\n\nYou can enable 'volumesnapshots' addon by running: 'minikube addons enable volumesnapshots'\n": "",

View File

@ -67,6 +67,7 @@
"Bind Address: {{.Address}}": "Dirección de enlace: {{.Address}}",
"Booting up control plane ...": "",
"Both driver={{.driver}} and vm-driver={{.vmd}} have been set.\n\n Since vm-driver is deprecated, minikube will default to driver={{.driver}}.\n\n If vm-driver is set in the global config, please run \"minikube config unset vm-driver\" to resolve this warning.\n\t\t\t": "Ambos driver={{.driver}} y vm-driver={{.vmd}} han sido establecidos.\n\n vm-driver ya es obsoleto, el por defecto de minikube será driver={{.driver}}.\n\n Si vm-driver está establecido en la configuracion global, ejecuta \"minikube config unset vm-driver\" para resolver esta advertencia.\n\t\t\t",
"Bridge CNI is incompatible with multi-node clusters, use a different CNI": "",
"Build a container image in minikube": "",
"Build a container image, using the container runtime.": "",
"CNI plug-in to use. Valid options: auto, bridge, calico, cilium, flannel, kindnet, or path to a CNI manifest (default: auto)": "Plug-in CNI para usar. Opciones validas: auto, bridge, calico, cilium, flannel, kindnet, o ruta a un manifiesto CNI (Por defecto: auto)",
@ -736,6 +737,7 @@
"Unpausing node {{.name}} ... ": "",
"Unset the KUBECONFIG environment variable, or verify that it does not point to an empty or otherwise invalid path": "",
"Unset variables instead of setting them": "",
"Update Docker to the latest minor version, this version is unsupported": "",
"Update kubeconfig in case of an IP or port change": "",
"Update server returned an empty list": "",
"Updating the running {{.driver_name}} \"{{.cluster}}\" {{.machine_type}} ...": "",
@ -802,12 +804,14 @@
"You have chosen to disable the CNI but the \\\"{{.name}}\\\" container runtime requires CNI": "",
"You may need to manually remove the \"{{.name}}\" VM from your hypervisor": "Puede que tengas que retirar manualmente la VM \"{{.name}}\" de tu hipervisor",
"You may need to stop the Hyper-V Manager and run `minikube delete` again.": "",
"You might be using an amd64 version of minikube on a M1 Mac, use the arm64 version of minikube instead": "",
"You must specify a service name": "",
"Your GCP credentials will now be mounted into every pod created in the {{.name}} cluster.": "",
"Your cgroup does not allow setting memory.": "",
"Your host does not support KVM virtualization. Ensure that qemu-kvm is installed, and run 'virt-host-validate' to debug the problem": "",
"Your host does not support virtualization. If you are running minikube within a VM, try '--driver=docker'. Otherwise, enable virtualization in your BIOS": "",
"Your host is failing to route packets to the minikube VM. If you have VPN software, try turning it off or configuring it so that it does not re-route traffic to the VM IP. If not, check your VM environment routing options.": "",
"Your minikube certs likely expired, as a workaround, clear your minikube home dir `minikube delete --all --purge`": "",
"Your minikube config refers to an unsupported driver. Erase ~/.minikube, and try again.": "",
"Your minikube vm is not running, try minikube start.": "",
"[WARNING] For full functionality, the 'csi-hostpath-driver' addon requires the 'volumesnapshots' addon to be enabled.\n\nYou can enable 'volumesnapshots' addon by running: 'minikube addons enable volumesnapshots'\n": "",

View File

@ -67,6 +67,7 @@
"Bind Address: {{.Address}}": "Adresse de liaison : {{.Address}}",
"Booting up control plane ...": "Démarrage du plan de contrôle ...",
"Both driver={{.driver}} and vm-driver={{.vmd}} have been set.\n\n Since vm-driver is deprecated, minikube will default to driver={{.driver}}.\n\n If vm-driver is set in the global config, please run \"minikube config unset vm-driver\" to resolve this warning.\n\t\t\t": "",
"Bridge CNI is incompatible with multi-node clusters, use a different CNI": "",
"Build a container image in minikube": "",
"Build a container image, using the container runtime.": "",
"CNI plug-in to use. Valid options: auto, bridge, calico, cilium, flannel, kindnet, or path to a CNI manifest (default: auto)": "",
@ -734,6 +735,7 @@
"Unpausing node {{.name}} ... ": "",
"Unset the KUBECONFIG environment variable, or verify that it does not point to an empty or otherwise invalid path": "",
"Unset variables instead of setting them": "",
"Update Docker to the latest minor version, this version is unsupported": "",
"Update kubeconfig in case of an IP or port change": "",
"Update server returned an empty list": "",
"Updating the running {{.driver_name}} \"{{.cluster}}\" {{.machine_type}} ...": "Mise à jour du {{.machine_type}} {{.driver_name}} en marche \"{{.cluster}}\" ...",
@ -803,12 +805,14 @@
"You have chosen to disable the CNI but the \\\"{{.name}}\\\" container runtime requires CNI": "",
"You may need to manually remove the \"{{.name}}\" VM from your hypervisor": "Vous devrez peut-être supprimer la VM \"{{.name}}\" manuellement de votre hyperviseur.",
"You may need to stop the Hyper-V Manager and run `minikube delete` again.": "",
"You might be using an amd64 version of minikube on a M1 Mac, use the arm64 version of minikube instead": "",
"You must specify a service name": "",
"Your GCP credentials will now be mounted into every pod created in the {{.name}} cluster.": "",
"Your cgroup does not allow setting memory.": "",
"Your host does not support KVM virtualization. Ensure that qemu-kvm is installed, and run 'virt-host-validate' to debug the problem": "",
"Your host does not support virtualization. If you are running minikube within a VM, try '--driver=docker'. Otherwise, enable virtualization in your BIOS": "",
"Your host is failing to route packets to the minikube VM. If you have VPN software, try turning it off or configuring it so that it does not re-route traffic to the VM IP. If not, check your VM environment routing options.": "",
"Your minikube certs likely expired, as a workaround, clear your minikube home dir `minikube delete --all --purge`": "",
"Your minikube config refers to an unsupported driver. Erase ~/.minikube, and try again.": "",
"Your minikube vm is not running, try minikube start.": "",
"[WARNING] For full functionality, the 'csi-hostpath-driver' addon requires the 'volumesnapshots' addon to be enabled.\n\nYou can enable 'volumesnapshots' addon by running: 'minikube addons enable volumesnapshots'\n": "",

View File

@ -65,6 +65,7 @@
"Bind Address: {{.Address}}": "アドレスをバインドします: {{.Address}}",
"Booting up control plane ...": "Control Plane を起動しています...",
"Both driver={{.driver}} and vm-driver={{.vmd}} have been set.\n\n Since vm-driver is deprecated, minikube will default to driver={{.driver}}.\n\n If vm-driver is set in the global config, please run \"minikube config unset vm-driver\" to resolve this warning.\n\t\t\t": "",
"Bridge CNI is incompatible with multi-node clusters, use a different CNI": "",
"Build a container image in minikube": "",
"Build a container image, using the container runtime.": "",
"CNI plug-in to use. Valid options: auto, bridge, calico, cilium, flannel, kindnet, or path to a CNI manifest (default: auto)": "",
@ -731,6 +732,7 @@
"Unpausing node {{.name}} ... ": "",
"Unset the KUBECONFIG environment variable, or verify that it does not point to an empty or otherwise invalid path": "",
"Unset variables instead of setting them": "",
"Update Docker to the latest minor version, this version is unsupported": "",
"Update kubeconfig in case of an IP or port change": "IP アドレスやポート番号が変わった場合に kubeconfig を更新します",
"Update server returned an empty list": "",
"Updating the running {{.driver_name}} \"{{.cluster}}\" {{.machine_type}} ...": "起動中の {{.driver_name}} \"{{.cluster}}\" {{.machine_type}} を更新しています...",
@ -801,12 +803,14 @@
"You have chosen to disable the CNI but the \\\"{{.name}}\\\" container runtime requires CNI": "",
"You may need to manually remove the \"{{.name}}\" VM from your hypervisor": "ハイパーバイザから「{{.name}}」VM を手動で削除することが必要な可能性があります",
"You may need to stop the Hyper-V Manager and run `minikube delete` again.": "Hyper-V マネージャを停止して、「 minikube delete 」を再実行する必要があるかもしれません ",
"You might be using an amd64 version of minikube on a M1 Mac, use the arm64 version of minikube instead": "",
"You must specify a service name": "サービスの名前を明示する必要があります",
"Your GCP credentials will now be mounted into every pod created in the {{.name}} cluster.": "",
"Your cgroup does not allow setting memory.": "",
"Your host does not support KVM virtualization. Ensure that qemu-kvm is installed, and run 'virt-host-validate' to debug the problem": "ホストマシーンは KVM 仮想化をサポートしていません。 qemu-kvm がインストールされていることを確認してください。「 virt-host-validate 」を実行して、デバッグしてください",
"Your host does not support virtualization. If you are running minikube within a VM, try '--driver=docker'. Otherwise, enable virtualization in your BIOS": "ホストマシーンは仮想化をサポートしていません。もし VM 内で minikube を動かすのであれば、「 --driver=docker 」を試してください。そうでなければ、 BIOS で仮想化を有効にしてください",
"Your host is failing to route packets to the minikube VM. If you have VPN software, try turning it off or configuring it so that it does not re-route traffic to the VM IP. If not, check your VM environment routing options.": "ホストマシーンが minikube の VM にパケットをルーティングすることができていません。もし VPN を有効しているのであれば、VPN を無効にする、あるいは VM の IP アドレスに再ルーティングしないように設定してください。もし VPN を使用していないのであれば、 VM 環境のルーティング周りのオプションを確認してください",
"Your minikube certs likely expired, as a workaround, clear your minikube home dir `minikube delete --all --purge`": "",
"Your minikube config refers to an unsupported driver. Erase ~/.minikube, and try again.": "今の minikube の設定はサポートされていないドライバーを参照しています。 ~/.minikube を削除して、もう一度試してください",
"Your minikube vm is not running, try minikube start.": "minikube の VM が動いていません。以下のコマンドを試してみてください。 minikube start",
"[WARNING] For full functionality, the 'csi-hostpath-driver' addon requires the 'volumesnapshots' addon to be enabled.\n\nYou can enable 'volumesnapshots' addon by running: 'minikube addons enable volumesnapshots'\n": "",

View File

@ -72,6 +72,7 @@
"Block until the apiserver is servicing API requests": "apiserver 가 API 요청을 서비스할 때까지 막습니다",
"Booting up control plane ...": "컨트롤 플레인이 부팅...",
"Both driver={{.driver}} and vm-driver={{.vmd}} have been set.\n\n Since vm-driver is deprecated, minikube will default to driver={{.driver}}.\n\n If vm-driver is set in the global config, please run \"minikube config unset vm-driver\" to resolve this warning.\n\t\t\t": "",
"Bridge CNI is incompatible with multi-node clusters, use a different CNI": "",
"Build a container image in minikube": "minikube 내 컨테이너 이미지를 빌드합니다",
"Build a container image, using the container runtime.": "컨테이너 런타임을 사용하여 컨테이너 이미지를 빌드합니다.",
"CNI plug-in to use. Valid options: auto, bridge, calico, cilium, flannel, kindnet, or path to a CNI manifest (default: auto)": "",
@ -740,6 +741,7 @@
"Unpausing node {{.name}} ... ": "",
"Unset the KUBECONFIG environment variable, or verify that it does not point to an empty or otherwise invalid path": "",
"Unset variables instead of setting them": "",
"Update Docker to the latest minor version, this version is unsupported": "",
"Update kubeconfig in case of an IP or port change": "",
"Update server returned an empty list": "",
"Updating the running {{.driver_name}} \"{{.cluster}}\" {{.machine_type}} ...": "실행중인 {{.driver_name}} \"{{.cluster}}\" {{.machine_type}} 를 업데이트 하는 중 ...",
@ -805,6 +807,7 @@
"You have chosen to disable the CNI but the \\\"{{.name}}\\\" container runtime requires CNI": "",
"You may need to manually remove the \"{{.name}}\" VM from your hypervisor": "",
"You may need to stop the Hyper-V Manager and run `minikube delete` again.": "",
"You might be using an amd64 version of minikube on a M1 Mac, use the arm64 version of minikube instead": "",
"You must specify a service name": "service 이름을 명시해야 합니다",
"Your GCP credentials will now be mounted into every pod created in the {{.name}} cluster.": "",
"Your cgroup does not allow setting memory.": "",
@ -812,6 +815,7 @@
"Your host does not support virtualization. If you are running minikube within a VM, try '--driver=docker'. Otherwise, enable virtualization in your BIOS": "",
"Your host does not support virtualization. If you are running minikube within a VM, try '--driver=none'. Otherwise, enable virtualization in your BIOS": "호스트가 가상화를 지원하지 않습니다. 가상 머신 안에서 minikube 를 실행 중인 경우, '--driver=none' 로 시도하세요. 그렇지 않다면, BIOS 에서 가상화를 활성화하세요",
"Your host is failing to route packets to the minikube VM. If you have VPN software, try turning it off or configuring it so that it does not re-route traffic to the VM IP. If not, check your VM environment routing options.": "",
"Your minikube certs likely expired, as a workaround, clear your minikube home dir `minikube delete --all --purge`": "",
"Your minikube config refers to an unsupported driver. Erase ~/.minikube, and try again.": "minikube config 가 미지원 드라이버를 참조하고 있습니다. ~/.minikube 를 제거한 후, 다시 시도하세요",
"Your minikube vm is not running, try minikube start.": "minikube 가상 머신이 실행 중이 아닙니다, minikube start 를 시도하세요",
"[WARNING] For full functionality, the 'csi-hostpath-driver' addon requires the 'volumesnapshots' addon to be enabled.\n\nYou can enable 'volumesnapshots' addon by running: 'minikube addons enable volumesnapshots'\n": "",

View File

@ -70,6 +70,7 @@
"Bind Address: {{.Address}}": "",
"Booting up control plane ...": "",
"Both driver={{.driver}} and vm-driver={{.vmd}} have been set.\n\n Since vm-driver is deprecated, minikube will default to driver={{.driver}}.\n\n If vm-driver is set in the global config, please run \"minikube config unset vm-driver\" to resolve this warning.\n\t\t\t": "",
"Bridge CNI is incompatible with multi-node clusters, use a different CNI": "",
"Build a container image in minikube": "",
"Build a container image, using the container runtime.": "",
"CNI plug-in to use. Valid options: auto, bridge, calico, cilium, flannel, kindnet, or path to a CNI manifest (default: auto)": "",
@ -747,6 +748,7 @@
"Unpausing node {{.name}} ... ": "",
"Unset the KUBECONFIG environment variable, or verify that it does not point to an empty or otherwise invalid path": "",
"Unset variables instead of setting them": "",
"Update Docker to the latest minor version, this version is unsupported": "",
"Update kubeconfig in case of an IP or port change": "",
"Update server returned an empty list": "",
"Updating the running {{.driver_name}} \"{{.cluster}}\" {{.machine_type}} ...": "",
@ -814,12 +816,14 @@
"You have chosen to disable the CNI but the \\\"{{.name}}\\\" container runtime requires CNI": "",
"You may need to manually remove the \"{{.name}}\" VM from your hypervisor": "",
"You may need to stop the Hyper-V Manager and run `minikube delete` again.": "",
"You might be using an amd64 version of minikube on a M1 Mac, use the arm64 version of minikube instead": "",
"You must specify a service name": "Musisz podać nazwę serwisu",
"Your GCP credentials will now be mounted into every pod created in the {{.name}} cluster.": "",
"Your cgroup does not allow setting memory.": "",
"Your host does not support KVM virtualization. Ensure that qemu-kvm is installed, and run 'virt-host-validate' to debug the problem": "Twoje środowisko nie wspiera wirtualizacji KVM. Upewnij się, że qemu-kvm jest zainstalowane i uruchom 'virt-host-validate' aby rozwiązać problem.",
"Your host does not support virtualization. If you are running minikube within a VM, try '--driver=docker'. Otherwise, enable virtualization in your BIOS": "",
"Your host is failing to route packets to the minikube VM. If you have VPN software, try turning it off or configuring it so that it does not re-route traffic to the VM IP. If not, check your VM environment routing options.": "",
"Your minikube certs likely expired, as a workaround, clear your minikube home dir `minikube delete --all --purge`": "",
"Your minikube config refers to an unsupported driver. Erase ~/.minikube, and try again.": "",
"Your minikube vm is not running, try minikube start.": "",
"[WARNING] For full functionality, the 'csi-hostpath-driver' addon requires the 'volumesnapshots' addon to be enabled.\n\nYou can enable 'volumesnapshots' addon by running: 'minikube addons enable volumesnapshots'\n": "",

View File

@ -62,6 +62,7 @@
"Bind Address: {{.Address}}": "",
"Booting up control plane ...": "",
"Both driver={{.driver}} and vm-driver={{.vmd}} have been set.\n\n Since vm-driver is deprecated, minikube will default to driver={{.driver}}.\n\n If vm-driver is set in the global config, please run \"minikube config unset vm-driver\" to resolve this warning.\n\t\t\t": "",
"Bridge CNI is incompatible with multi-node clusters, use a different CNI": "",
"Build a container image in minikube": "",
"Build a container image, using the container runtime.": "",
"CNI plug-in to use. Valid options: auto, bridge, calico, cilium, flannel, kindnet, or path to a CNI manifest (default: auto)": "",
@ -680,6 +681,7 @@
"Unpausing node {{.name}} ... ": "",
"Unset the KUBECONFIG environment variable, or verify that it does not point to an empty or otherwise invalid path": "",
"Unset variables instead of setting them": "",
"Update Docker to the latest minor version, this version is unsupported": "",
"Update kubeconfig in case of an IP or port change": "",
"Update server returned an empty list": "",
"Updating the running {{.driver_name}} \"{{.cluster}}\" {{.machine_type}} ...": "",
@ -742,12 +744,14 @@
"You have chosen to disable the CNI but the \\\"{{.name}}\\\" container runtime requires CNI": "",
"You may need to manually remove the \"{{.name}}\" VM from your hypervisor": "",
"You may need to stop the Hyper-V Manager and run `minikube delete` again.": "",
"You might be using an amd64 version of minikube on a M1 Mac, use the arm64 version of minikube instead": "",
"You must specify a service name": "",
"Your GCP credentials will now be mounted into every pod created in the {{.name}} cluster.": "",
"Your cgroup does not allow setting memory.": "",
"Your host does not support KVM virtualization. Ensure that qemu-kvm is installed, and run 'virt-host-validate' to debug the problem": "",
"Your host does not support virtualization. If you are running minikube within a VM, try '--driver=docker'. Otherwise, enable virtualization in your BIOS": "",
"Your host is failing to route packets to the minikube VM. If you have VPN software, try turning it off or configuring it so that it does not re-route traffic to the VM IP. If not, check your VM environment routing options.": "",
"Your minikube certs likely expired, as a workaround, clear your minikube home dir `minikube delete --all --purge`": "",
"Your minikube config refers to an unsupported driver. Erase ~/.minikube, and try again.": "",
"Your minikube vm is not running, try minikube start.": "",
"[WARNING] For full functionality, the 'csi-hostpath-driver' addon requires the 'volumesnapshots' addon to be enabled.\n\nYou can enable 'volumesnapshots' addon by running: 'minikube addons enable volumesnapshots'\n": "",

View File

@ -82,6 +82,7 @@
"Block until the apiserver is servicing API requests": "阻塞直到 apiserver 为 API 请求提供服务",
"Booting up control plane ...": "",
"Both driver={{.driver}} and vm-driver={{.vmd}} have been set.\n\n Since vm-driver is deprecated, minikube will default to driver={{.driver}}.\n\n If vm-driver is set in the global config, please run \"minikube config unset vm-driver\" to resolve this warning.\n\t\t\t": "",
"Bridge CNI is incompatible with multi-node clusters, use a different CNI": "",
"Build a container image in minikube": "",
"Build a container image, using the container runtime.": "",
"CNI plug-in to use. Valid options: auto, bridge, calico, cilium, flannel, kindnet, or path to a CNI manifest (default: auto)": "",
@ -842,6 +843,7 @@
"Unpausing node {{.name}} ... ": "",
"Unset the KUBECONFIG environment variable, or verify that it does not point to an empty or otherwise invalid path": "",
"Unset variables instead of setting them": "",
"Update Docker to the latest minor version, this version is unsupported": "",
"Update kubeconfig in case of an IP or port change": "",
"Update server returned an empty list": "",
"Updating the running {{.driver_name}} \"{{.cluster}}\" {{.machine_type}} ...": "",
@ -918,12 +920,14 @@
"You have chosen to disable the CNI but the \\\"{{.name}}\\\" container runtime requires CNI": "",
"You may need to manually remove the \"{{.name}}\" VM from your hypervisor": "您可能需要从管理程序中手动移除“{{.name}}”虚拟机",
"You may need to stop the Hyper-V Manager and run `minikube delete` again.": "",
"You might be using an amd64 version of minikube on a M1 Mac, use the arm64 version of minikube instead": "",
"You must specify a service name": "",
"Your GCP credentials will now be mounted into every pod created in the {{.name}} cluster.": "",
"Your cgroup does not allow setting memory.": "",
"Your host does not support KVM virtualization. Ensure that qemu-kvm is installed, and run 'virt-host-validate' to debug the problem": "",
"Your host does not support virtualization. If you are running minikube within a VM, try '--driver=docker'. Otherwise, enable virtualization in your BIOS": "",
"Your host is failing to route packets to the minikube VM. If you have VPN software, try turning it off or configuring it so that it does not re-route traffic to the VM IP. If not, check your VM environment routing options.": "",
"Your minikube certs likely expired, as a workaround, clear your minikube home dir `minikube delete --all --purge`": "",
"Your minikube config refers to an unsupported driver. Erase ~/.minikube, and try again.": "",
"Your minikube vm is not running, try minikube start.": "",
"[WARNING] For full functionality, the 'csi-hostpath-driver' addon requires the 'volumesnapshots' addon to be enabled.\n\nYou can enable 'volumesnapshots' addon by running: 'minikube addons enable volumesnapshots'\n": "",