create kic node: create container: Windows does not support privileged mode. #7352
Comments
tstromberg
changed the title
tstromberg
added
co/docker-driver
|
I tried looking for answers around this -- but came up short. Can you check that your Docker for Desktop install is up-to-date? Also, can you check that Windows Containers are disabled in Docker? I heard there were some conflicts when it is enabled. |
|
Does Docker-for-Windows support running privileged containers now ? It used not to....
https://github.com/moby/moby/blob/v19.03.8/runconfig/hostconfig_windows.go#L80_L82 Should be easy to verify, with something like |
|
@afbjorklund |
|
@tstromberg the docker is up-to-date. |
|
@devika-28 - disable Windows Containers. |
|
@tstromberg after disabling the container, The docker has stopped working
* minikube v1.9.0 on Microsoft Windows 10 Enterprise 10.0.18362 Build 18362
* Using the docker driver based on existing profile
! 'docker' driver reported an issue: exit status 1
X Unable to start VM after repeated tries. Please try {{'minikube delete' if possible: recreate: creating host: create: creating: create kic node: creating volume for minikube container: output error during connect: Post http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.40/volumes/create: open //./pipe/docker_engine: The system cannot find the file specified. In the default daemon configuration on Windows, the docker client must be run elevated to connect. This error may also indicate that the docker daemon is not running.
the docker desktop has stopped working:
Required Windows feature(s) not enabled : Containers.
Docker Desktop will exit.
|
|
@devika-28 do you mind restarting your docker after disabling windows containers and try again ? |
|
@devika-28 if you can confirm disabling windows containers and restarting fixes this. we can add this to the solution message and help user fix the problem without an ugly error message |
medyagh
added
the
needs-solution-message
Windows does not support privileged mode (Azure: Microsoft Windows Server 2019 Datacenter) Steps to reproduce the issue:
There was not config.json file like in #5529 so I excecuted
and got config.json file
{
"Name": "minikube",
"KeepContext": false,
"EmbedCerts": false,
"MinikubeISO": "",
"Memory": 2200,
"CPUs": 2,
"DiskSize": 20000,
"Driver": "docker",
"HyperkitVpnKitSock": "",
"HyperkitVSockPorts": [],
"DockerEnv": null,
"InsecureRegistry": null,
"RegistryMirror": null,
"HostOnlyCIDR": "192.168.99.1/24",
"HypervVirtualSwitch": "",
"HypervUseExternalSwitch": false,
"HypervExternalAdapter": "",
"KVMNetwork": "default",
"KVMQemuURI": "qemu:///system",
"KVMGPU": false,
"KVMHidden": false,
"DockerOpt": null,
"DisableDriverMounts": false,
"NFSShare": [],
"NFSSharesRoot": "/nfsshares",
"UUID": "",
"NoVTXCheck": false,
"DNSProxy": false,
"HostDNSResolver": true,
"HostOnlyNicType": "virtio",
"NatNicType": "virtio",
"KubernetesConfig": {
"KubernetesVersion": "v1.18.0",
"ClusterName": "minikube",
"APIServerName": "minikubeCA",
"APIServerNames": null,
"APIServerIPs": null,
"DNSDomain": "cluster.local",
"ContainerRuntime": "docker",
"CRISocket": "",
"NetworkPlugin": "",
"FeatureGates": "",
"ServiceCIDR": "10.96.0.0/12",
"ImageRepository": "",
"ExtraOptions": [
{
"Component": "kubeadm",
"Key": "pod-network-cidr",
"Value": "10.244.0.0/16"
}
],
"ShouldLoadCachedImages": true,
"EnableDefaultCNI": false,
"NodeIP": "",
"NodePort": 0,
"NodeName": ""
},
"Nodes": [
{
"Name": "m01",
"IP": "",
"Port": 8443,
"KubernetesVersion": "v1.18.0",
"ControlPlane": true,
"Worker": true
}
],
"Addons": null,
"VerifyComponents": {
"apiserver": true,
"system_pods": true
}
}
but minikube did not started
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
@medyagh, I also disabled Windows Containers but it did not change the situation
PS C:\Users\mika> minikube delete
I0424 17:13:15.215891 2344 kubelet.go:43] stopping kubelet ... stderr: stderr: stderr:
X Failed to start docker container. "minikube start" may fix it.: recreate: creating host: create: creating: create kic node: create container: failed args: [run -d -t --privileged --security-opt seccomp=unconfined --tmpfs /tmp --tmpfs /run -v /lib/modules:/lib/modules:ro --hostname minikube --name minikube --label created_by.minikube.sigs.k8s.io=true --label name.minikube.sigs.k8s.io=minikube --label role.minikube.sigs.k8s.io= --label mode.minikube.sigs.k8s.io=minikube --volume minikube:/var --cpus=2 --memory=2200mb --expose 8443 --publish=127.0.0.1::8443 --publish=127.0.0.1::22 --publish=127.0.0.1::2376 gcr.io/k8s-minikube/kicbase:v0.0.8@sha256:2f3380ebf1bb0c75b0b47160fd4e61b7b8fef0f1f32f9def108d3eada50a7a81] output: docker: Error response from daemon: Windows does not support privileged mode.
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
PS C:\Users\mika> Stop-Service docker
PS C:\Users\mika>
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
**Full output of failed command:**
PS C:\Users\mika> Start-Service docker
! 'docker' driver reported an issue: exit status 1
I0424 17:51:26.689215 7040 start.go:1100] auto setting extra-config to "kubeadm.pod-network-cidr=10.244.0.0/16".
I0424 17:51:39.058874 7040 kubelet.go:43] stopping kubelet ... stderr: stderr: stderr:
I0424 17:51:58.776198 7040 kubelet.go:43] stopping kubelet ... stderr: stderr: stderr:
X Failed to start docker container. "minikube start" may fix it.: recreate: creating host: create: creating: create kic node: create container: failed args: [run -d -t --privileged --security-opt seccomp=unconfined --tmpfs /tmp --tmpfs /run -v /lib/modules:/lib/modules:ro --hostname minikube --name minikube --label created_by.minikube.sigs.k8s.io=true --label name.minikube.sigs.k8s.io=minikube --label role.minikube.sigs.k8s.io= --label mode.minikube.sigs.k8s.io=minikube --volume minikube:/var --cpus=2 --memory=2200mb --expose 8443 --publish=127.0.0.1::8443 --publish=127.0.0.1::22 --publish=127.0.0.1::2376 gcr.io/k8s-minikube/kicbase:v0.0.8@sha256:2f3380ebf1bb0c75b0b47160fd4e61b7b8fef0f1f32f9def108d3eada50a7a81] output: docker: Error response from daemon: Windows does not support privileged mode.
Optional: Full output of
PS C:\Users\mika> minikube logs
*
X Unable to get machine status: state: "docker inspect -f {{.State.Status}} minikube" failed: exit status 1: Template parsing error: template: :1:8: executing "" at <.State.Status>: map has no entry for key "State"
|
|
@mikalegall I had this problem on windows, and I noticed the only way to fix it was The first time it was showing it was using Linux Containers but when I ran minikube I got same error as you. the only way to verify is in terminal run then in os type it should say Linux and not Windows. (if it says winodwos, try to click on Docker Desktop and Switch to linux Containers) that fixed my issue, do u mind trying again? I am gonna make a PR that will check for OsType before creating the container. |
|
I just installed docker for desktop on a fresh windows and I noticed the Installation Processes has checked "enabled Windows features" by default. so if you click next, by default your docker desktop will be a windows container. |
|
so here is the Irony I talked about in screenshots: docker info shows it is Windows Containers
this is defenitaly a Docker Desktop Bug, but we could be smarter and try Docker Info before creating and make sure |
|
@devika-28 @mikalegall if you like u can download the binary from this PR and try it on your machine. |
|
macos is also. Failed to start docker container. "minikube start" may fix it.: recreate: creating host: create: creating: create kic node: create container: failed args: [run -d -t --privileged --security-opt seccomp=unconfined --tmpfs /tmp --tmpfs /run -v /lib/modules:/lib/modules:ro --hostname minikube --name minikube --label created_by.minikube.sigs.k8s.io=true --label name.minikube.sigs.k8s.io=minikube --label role.minikube.sigs.k8s.io= --label mode.minikube.sigs.k8s.io=minikube --volume minikube:/var --cpus=2 --memory=1989mb --expose 8443 --publish=127.0.0.1::8443 --publish=127.0.0.1::22 --publish=127.0.0.1::2376 gcr.io/k8s-minikube/kicbase:v0.0.8@sha256:2f3380ebf1bb0c75b0b47160fd4e61b7b8fef0f1f32f9def108d3eada50a7a81] output: Unable to find image 'gcr.io/k8s-minikube/kicbase:v0.0.8@sha256:2f3380ebf1bb0c75b0b47160fd4e61b7b8fef0f1f32f9def108d3eada50a7a81' locally |
Okay and thank you @medyagh |
command; minikube start --driver=docker
Steps to reproduce the issue:
step 1. choco install minikube
step 2. minikube start
the "--alsologtostderr" flag output:
Full output of failed command:
Optional: Full output of
minikube logscommand:Checked the virtualization support on windows using command "systeminfo"
the result was:
"Hyper-V Requirements: A hypervisor has been detected. Features required for Hyper-V will not be displayed."
The text was updated successfully, but these errors were encountered: