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
I'm trying to run 'minikube start' on Windows 10 home after installing minikube and placing kubectl.exe in a folder with an environment variable pointing there, but I'm getting the below error.
I've also put KUBECONFIG=C:\Users****.kube\config
Which points to a config file I've created using kubectl.
The exact command to reproduce the issue:
minikube start
The full output of the command that failed:
C:\WINDOWS\system32>minikube start
minikube v1.6.0 on Microsoft Windows 10 Home 10.0.18362 Build 18362
KUBECONFIG=C:\Users****.kube\config
Selecting 'virtualbox' driver from existing profile (alternates: [hyperv])
Tip: Use 'minikube start -p ' to create a new cluster, or 'minikube delete' to delete this one.
Using the running virtualbox "minikube" VM ...
Waiting for the host to be provisioned ...
Found network options:
NO_PROXY=192.168.99.100
no_proxy=192.168.99.100
Preparing Kubernetes v1.17.0 on Docker '19.03.5' ...
env NO_PROXY=192.168.99.100
env NO_PROXY=192.168.99.100
X Failed to setup kubeconfig: writing kubeconfig: Error writing file C:\Users*.kube\config: error acquiring lock for C:\Users*.kube\config: timeout acquiring mutex
*
Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
Dec 11 12:12:17 minikube dockerd[2455]: time="2019-12-11T12:12:17.098914651Z" level=warning msg="could not use snapshotter btrfs in metadata plugin" error="path /var/lib/docker/containerd/daemon/io.containerd.snapshotter.v1.btrfs must be a btrfs filesystem to be used with the btrfs snapshotter"
Dec 11 12:12:17 minikube dockerd[2455]: time="2019-12-11T12:12:17.098968051Z" level=warning msg="could not use snapshotter aufs in metadata plugin" error="modprobe aufs failed: "modprobe: FATAL: Module aufs not found in directory /lib/modules/4.19.81\n": exit status 1"
Dec 11 12:12:17 minikube dockerd[2455]: time="2019-12-11T12:12:17.099034119Z" level=warning msg="could not use snapshotter zfs in metadata plugin" error="path /var/lib/docker/containerd/daemon/io.containerd.snapshotter.v1.zfs must be a zfs filesystem to be used with the zfs snapshotter: skip plugin"
Dec 11 12:12:17 minikube dockerd[2455]: time="2019-12-11T12:12:17.118757492Z" level=info msg="scheme "unix" not registered, fallback to default scheme" module=grpc
Dec 11 12:12:17 minikube dockerd[2455]: time="2019-12-11T12:12:17.118775311Z" level=info msg="ccResolverWrapper: sending update to cc: {[{unix:///var/run/docker/containerd/containerd.sock 0 }] }" module=grpc
Dec 11 12:12:17 minikube dockerd[2455]: time="2019-12-11T12:12:17.118787214Z" level=info msg="ClientConn switching balancer to "pick_first"" module=grpc
Dec 11 12:12:17 minikube dockerd[2455]: time="2019-12-11T12:12:17.139130542Z" level=warning msg="Your kernel does not support cgroup blkio weight"
Dec 11 12:12:17 minikube dockerd[2455]: time="2019-12-11T12:12:17.139246598Z" level=warning msg="Your kernel does not support cgroup blkio weight_device"
Dec 11 12:12:17 minikube dockerd[2455]: time="2019-12-11T12:12:17.139295503Z" level=warning msg="Your kernel does not support cgroup blkio throttle.read_bps_device"
Dec 11 12:12:17 minikube dockerd[2455]: time="2019-12-11T12:12:17.139343960Z" level=warning msg="Your kernel does not support cgroup blkio throttle.write_bps_device"
Dec 11 12:12:17 minikube dockerd[2455]: time="2019-12-11T12:12:17.139386837Z" level=warning msg="Your kernel does not support cgroup blkio throttle.read_iops_device"
Dec 11 12:12:17 minikube dockerd[2455]: time="2019-12-11T12:12:17.139427561Z" level=warning msg="Your kernel does not support cgroup blkio throttle.write_iops_device"
Dec 11 12:12:17 minikube dockerd[2455]: time="2019-12-11T12:12:17.139692589Z" level=info msg="Loading containers: start."
Dec 11 12:12:17 minikube dockerd[2455]: time="2019-12-11T12:12:17.219098819Z" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address"
Dec 11 12:12:17 minikube dockerd[2455]: time="2019-12-11T12:12:17.263440611Z" level=info msg="Loading containers: done."
Dec 11 12:12:17 minikube dockerd[2455]: time="2019-12-11T12:12:17.294074817Z" level=info msg="Daemon has completed initialization"
Dec 11 12:12:17 minikube dockerd[2455]: time="2019-12-11T12:12:17.311263350Z" level=info msg="API listen on /var/run/docker.sock"
Dec 11 12:12:17 minikube dockerd[2455]: time="2019-12-11T12:12:17.311540027Z" level=info msg="API listen on [::]:2376"
Dec 11 12:12:17 minikube systemd[1]: Started Docker Application Container Engine.
==> container status <==
time="2019-12-11T12:24:25Z" level=fatal msg="failed to connect: failed to connect, make sure you are running as root and the runtime has been started: context deadline exceeded"
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
==> dmesg <==
[ +0.000001] Any video related functionality will be severely degraded, and you may not even be able to suspend the system properly
[ +0.000001] Unless you actually understand what nomodeset does, you should reboot without enabling it
[ +0.187191] acpi PNP0A03:00: fail to add MMCONFIG information, can't access extended PCI configuration space under this bridge.
[ +28.776729] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[Dec11 12:12] systemd[1]: Failed to bump fs.file-max, ignoring: Invalid argument
[ +0.018762] systemd-fstab-generator[1349]: Ignoring "noauto" for root device
[ +0.001598] systemd[1]: File /usr/lib/systemd/system/systemd-journald.service:12 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling.
[ +0.000002] systemd[1]: Proceeding WITHOUT firewalling in effect! (This warning is only shown for the first loaded unit using IP firewalling.)
This issue appears to be a duplicate of #6058, do you mind if we move the conversation there?
Ths way we can centralize the content relating to the issue. If you feel that this issue is not in fact a duplicate, please re-open it using /reopen. If you have additional information to share, please add it to the new issue.
I'm trying to run 'minikube start' on Windows 10 home after installing minikube and placing kubectl.exe in a folder with an environment variable pointing there, but I'm getting the below error.
I've also put KUBECONFIG=C:\Users****.kube\config
Which points to a config file I've created using kubectl.
The exact command to reproduce the issue:
minikube start
The full output of the command that failed:
C:\WINDOWS\system32>minikube start
X Failed to setup kubeconfig: writing kubeconfig: Error writing file C:\Users*.kube\config: error acquiring lock for C:\Users*.kube\config: timeout acquiring mutex
*
The output of the
minikube logs
command:C:\WINDOWS\system32>minikube logs
The operating system version:
Windows 10 Home
The text was updated successfully, but these errors were encountered: