Closed satya8574 closed 2 years ago
Thank you for sharing your experience!
Could you please run minikube logs --file=logs.txt
and drag and drop the file into this issue.
This will help us isolate the problem further, thank you!
Thanks & Regard
SATYA PRAKASH 8574121213
On Thu, Jun 23, 2022 at 11:16 PM Steven Powell @.***> wrote:
Thank you for sharing your experience!
Could you please run minikube logs --file=logs.txt and drag and drop the file into this issue.
This will help us isolate the problem further, thank you!
— Reply to this email directly, view it on GitHub https://github.com/kubernetes/minikube/issues/14396#issuecomment-1164697761, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXCTFOYNX5A3PYQGPGROIJTVQSPGPANCNFSM5ZTGAHFA . You are receiving this because you authored the thread.Message ID: @.***>
==> Audit <==
--------- | ------------------ | ---------- | ------ | --------- | --------------------- | ---------- | Command | Args | Profile | User | Version | Start Time | End Time | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
start | --vm-driver=none | minikube | root | v1.26.0 | 27 Jun 22 07:27 UTC | |||||||||
--------- | ------------------ | ---------- | ------ | --------- | --------------------- | ---------- |
==> Last Start <==
Log file created at: 2022/06/27 07:27:25
Running on machine: ip-172-31-16-136
Binary: Built with gc go1.18.3 for linux/amd64
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
I0627 07:27:25.875816 4349 out.go:296] Setting OutFile to fd 1 ...
I0627 07:27:25.875941 4349 out.go:343] TERM=xterm,COLORTERM=, which probably does not support color
I0627 07:27:25.875948 4349 out.go:309] Setting ErrFile to fd 2...
I0627 07:27:25.875955 4349 out.go:343] TERM=xterm,COLORTERM=, which probably does not support color
I0627 07:27:25.876157 4349 root.go:329] Updating PATH: /root/.minikube/bin
W0627 07:27:25.876275 4349 root.go:307] Error reading config file at /root/.minikube/config/config.json: open /root/.minikube/config/config.json: no such file or directory
I0627 07:27:25.876532 4349 out.go:303] Setting JSON to false
I0627 07:27:25.877273 4349 start.go:115] hostinfo: {"hostname":"ip-172-31-16-136","uptime":363,"bootTime":1656314483,"procs":118,"os":"linux","platform":"ubuntu","platformFamily":"debian","platformVersion":"18.04","kernelVersion":"5.4.0-1078-aws","kernelArch":"x86_64","virtualizationSystem":"xen","virtualizationRole":"guest","hostId":"ec29433d-c9ff-0706-0f40-3c3a18299bd4"}
I0627 07:27:25.877357 4349 start.go:125] virtualization: xen guest
I0627 07:27:25.883040 4349 out.go:177] minikube v1.26.0 on Ubuntu 18.04 (xen/amd64)
I0627 07:27:25.887602 4349 driver.go:360] Setting default libvirt URI to qemu:///system
W0627 07:27:25.887657 4349 preload.go:295] Failed to list preload files: open /root/.minikube/cache/preloaded-tarball: no such file or directory
I0627 07:27:25.887679 4349 notify.go:193] Checking for updates...
I0627 07:27:25.891566 4349 out.go:177] Using the none driver based on user configuration
I0627 07:27:25.895467 4349 start.go:284] selected driver: none
I0627 07:27:25.895475 4349 start.go:805] validating driver "none" against
stderr: Failed to enable unit: Unit file cri-docker.socket does not exist.
W0627 07:27:27.768083 4349 out.go:239]
W0627 07:27:27.769041 4349 out.go:239] ╭─────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ If the above advice does not help, please let us know: │
│ https://github.com/kubernetes/minikube/issues/new/choose │
│ │
│ * Please run minikube logs --file=logs.txt
and attach logs.txt to the GitHub issue. │
│ │
╰─────────────────────────────────────────────────────────────────────────────────────────────╯
I0627 07:27:27.772365 4349 out.go:177]
Hi @satya8574, thanks for providing your logs.
Kubernetes v1.24 dropped support for Dockershim, so if you want to use the combination of the none driver, Kubernetes v1.24+, and the Docker container runtime you'll need to install cri-dockerd on your system, as listed in our requirements page.
Other options include using a different driver, using an older version of Kubernetes --kubernetes-version
, or using a different container runtime --container-runtime
.
Please try one of those solution and let me know if it resolves your issue, thanks
No !
Please Provide me required command in file for ubuntu 18.04 Like- PFA
Thanks & Regard
SATYA PRAKASH 8574121213
On Mon, Jun 27, 2022 at 10:48 PM Steven Powell @.***> wrote:
Hi @satya8574 https://github.com/satya8574, thanks for providing your logs.
Kubernetes v1.24 dropped support for Dockershim, so if you want to use the combination of the none driver, Kubernetes v1.24+, and the Docker container runtime you'll need to install cri-dockerd on your system, as listed in our requirements page https://minikube.sigs.k8s.io/docs/drivers/none/#requirements.
Other options include using a different driver https://minikube.sigs.k8s.io/docs/drivers/, using an older version of Kubernetes --kubernetes-version, or using a different container runtime --container-runtime.
Please try one of those solution and let me know if it resolves your issue, thanks
— Reply to this email directly, view it on GitHub https://github.com/kubernetes/minikube/issues/14396#issuecomment-1167634997, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXCTFO2NNSTA46KBLVXOOTLVRHO7XANCNFSM5ZTGAHFA . You are receiving this because you were mentioned.Message ID: @.***>
sudo apt update && apt -y install docker.io
install Kubectl now with the given link
curl -LO https://storage.googleapis.com/kubernetes-release/release/$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)/bin/linux/amd64/kubectl && chmod +x ./kubectl && sudo mv ./kubectl /usr/local/bin/kubectl
install Minikube with the given link
curl -Lo minikube https://storage.googleapis.com/minikube/releases/latest/minikube-linux-amd64 && chmod +x minikube && sudo mv minikube /usr/local/bin/
apt install conntrack
minikube start --vm-driver=none minikube status kubectl version kubectl get nodes
The link to the cri-dockerd install instructions are linked on the page I previously linked to you, here is the direct link to the documentation.
Going to close this issue to centralize these duplicated cri-docker
issues in https://github.com/kubernetes/minikube/issues/14410. If you have any further questions or comments please leave them in https://github.com/kubernetes/minikube/issues/14410, thank you.
Not Get Resolve still Same issue
Thanks & Regard
SATYA PRAKASH 8574121213
On Fri, Jul 1, 2022 at 4:14 AM Steven Powell @.***> wrote:
Going to close this issue to centralize these duplicated cri-docker issues in #14410 https://github.com/kubernetes/minikube/issues/14410. If you have any further questions or comments please leave them in #14410 https://github.com/kubernetes/minikube/issues/14410, thank you.
— Reply to this email directly, view it on GitHub https://github.com/kubernetes/minikube/issues/14396#issuecomment-1171745742, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXCTFO3JVPZYYMM5EZVGUTLVRYPOVANCNFSM5ZTGAHFA . You are receiving this because you were mentioned.Message ID: @.***>
Did you install cri-docker
?
Yes, I did.
Thanks & Regard
SATYA PRAKASH 8574121213
On Fri, Jul 1, 2022 at 9:38 PM Steven Powell @.***> wrote:
Did you install cri-docker?
— Reply to this email directly, view it on GitHub https://github.com/kubernetes/minikube/issues/14396#issuecomment-1172496482, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXCTFO2SBS52X65YWIH4T6LVR4JXFANCNFSM5ZTGAHFA . You are receiving this because you were mentioned.Message ID: @.***>
Dear steven , Can You please share me all the command to me on NotePad
Thanks & Regard
SATYA PRAKASH 8574121213
On Fri, Jul 1, 2022 at 10:08 PM Satya Sahani @.***> wrote:
Yes, I did.
Thanks & Regard
SATYA PRAKASH 8574121213
On Fri, Jul 1, 2022 at 9:38 PM Steven Powell @.***> wrote:
Did you install cri-docker?
— Reply to this email directly, view it on GitHub https://github.com/kubernetes/minikube/issues/14396#issuecomment-1172496482, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXCTFO2SBS52X65YWIH4T6LVR4JXFANCNFSM5ZTGAHFA . You are receiving this because you were mentioned.Message ID: @.***>
ls /usr/local/bin/cri-dockerd
ls /etc/systemd/system/cri-docker.service
ls /etc/systemd/systemcri-docker.socket
minikube delete
sudo -E minikube start --driver=none
Thanks, I'll check it out. Not Resoloved
Thanks & Regard
SATYA PRAKASH 8574121213
On Fri, Jul 1, 2022 at 11:28 PM Steven Powell @.***> wrote:
ls /usr/local/bin/cri-dockerd ls /etc/systemd/system/cri-docker.service ls /etc/systemd/systemcri-docker.socket minikube delete sudo -E minikube start --driver=none
— Reply to this email directly, view it on GitHub https://github.com/kubernetes/minikube/issues/14396#issuecomment-1172585583, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXCTFO36LS54ET3OEFDL5IDVR4WUXANCNFSM5ZTGAHFA . You are receiving this because you were mentioned.Message ID: @.***>
==> Audit <==
--------- | ------------------ | ---------- | ------ | --------- | --------------------- | ---------- | Command | Args | Profile | User | Version | Start Time | End Time | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
start | --driver=none | minikube | root | v1.26.0 | 02 Jul 22 15:54 UTC | |||||||||
start | --vm-driver=none | minikube | root | v1.26.0 | 02 Jul 22 15:55 UTC | |||||||||
--------- | ------------------ | ---------- | ------ | --------- | --------------------- | ---------- |
==> Last Start <==
Log file created at: 2022/07/02 15:55:18
Running on machine: ip-172-31-4-22
Binary: Built with gc go1.18.3 for linux/amd64
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
I0702 15:55:18.825904 2212 out.go:296] Setting OutFile to fd 1 ...
I0702 15:55:18.826021 2212 out.go:343] TERM=xterm,COLORTERM=, which probably does not support color
I0702 15:55:18.826026 2212 out.go:309] Setting ErrFile to fd 2...
I0702 15:55:18.826032 2212 out.go:343] TERM=xterm,COLORTERM=, which probably does not support color
I0702 15:55:18.826228 2212 root.go:329] Updating PATH: /root/.minikube/bin
W0702 15:55:18.826347 2212 root.go:307] Error reading config file at /root/.minikube/config/config.json: open /root/.minikube/config/config.json: no such file or directory
I0702 15:55:18.826457 2212 out.go:303] Setting JSON to false
I0702 15:55:18.827208 2212 start.go:115] hostinfo: {"hostname":"ip-172-31-4-22","uptime":241,"bootTime":1656777078,"procs":119,"os":"linux","platform":"ubuntu","platformFamily":"debian","platformVersion":"18.04","kernelVersion":"5.4.0-1078-aws","kernelArch":"x86_64","virtualizationSystem":"xen","virtualizationRole":"guest","hostId":"ec2bba33-9d1b-52dd-4666-69000823b5fb"}
I0702 15:55:18.827263 2212 start.go:125] virtualization: xen guest
I0702 15:55:18.830051 2212 out.go:177] minikube v1.26.0 on Ubuntu 18.04 (xen/amd64)
W0702 15:55:18.831943 2212 preload.go:295] Failed to list preload files: open /root/.minikube/cache/preloaded-tarball: no such file or directory
I0702 15:55:18.832141 2212 notify.go:193] Checking for updates...
I0702 15:55:18.832176 2212 config.go:178] Loaded profile config "minikube": Driver=none, ContainerRuntime=docker, KubernetesVersion=v1.24.1
I0702 15:55:18.832476 2212 exec_runner.go:51] Run: systemctl --version
I0702 15:55:18.836062 2212 driver.go:360] Setting default libvirt URI to qemu:///system
I0702 15:55:18.838118 2212 out.go:177] Using the none driver based on existing profile
I0702 15:55:18.839758 2212 start.go:284] selected driver: none
I0702 15:55:18.839772 2212 start.go:805] validating driver "none" against &{Name:minikube KeepContext:false EmbedCerts:false MinikubeISO: @.:9190bd2393eae887316c97a74370b7d5dad8f0b2ef91ac2662bc36f7ef8e0b95 Memory:2200 CPUs:2 DiskSize:20000 VMDriver: Driver:none HyperkitVpnKitSock: HyperkitVSockPorts:[] DockerEnv:[] ContainerVolumeMounts:[] InsecureRegistry:[] RegistryMirror:[] HostOnlyCIDR:192.168.59.1/24 HypervVirtualSwitch: HypervUseExternalSwitch:false HypervExternalAdapter: KVMNetwork:default KVMQemuURI:qemu:///system KVMGPU:false KVMHidden:false KVMNUMACount:1 APIServerPort:0 DockerOpt:[] DisableDriverMounts:false NFSShare:[] NFSSharesRoot:/nfsshares UUID: NoVTXCheck:false DNSProxy:false HostDNSResolver:true HostOnlyNicType:virtio NatNicType:virtio SSHIPAddress: SSHUser:root SSHKey: SSHPort:22 KubernetesConfig:{KubernetesVersion:v1.24.1 ClusterName:minikube Namespace:default APIServerName:minikubeCA APIServerNames:[] APIServerIPs:[] DNSDomain:cluster.local ContainerRuntime:docker CRISocket: NetworkPlugin: FeatureGates: ServiceCIDR:10.96.0.0/12 ImageRepository: LoadBalancerStartIP: LoadBalancerEndIP: CustomIngressCert: RegistryAliases: ExtraOptions:[{Component:kubelet Key:resolv-conf Value:/run/systemd/resolve/resolv.conf}] ShouldLoadCachedImages:false EnableDefaultCNI:false CNI: NodeIP: NodePort:8443 NodeName:} Nodes:[{Name:m01 IP:172.31.4.22 Port:8443 KubernetesVersion:v1.24.1 ContainerRuntime:docker ControlPlane:true Worker:true}] Addons:map[] CustomAddonImages:map[] CustomAddonRegistries:map[] VerifyComponents:map[apiserver:true system_pods:true] StartHostTimeout:6m0s ScheduledStop:
stderr:
I0702 15:55:18.855200 2212 exec_runner.go:51] Run: sudo systemctl is-active --quiet service kubelet
I0702 15:55:18.864664 2212 fix.go:103] recreateIfNeeded on minikube: state=Stopped err=
stderr: Failed to enable unit: Unit file cri-docker.socket does not exist.
W0702 15:55:19.706897 2212 out.go:239]
W0702 15:55:19.707919 2212 out.go:239] ╭─────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ If the above advice does not help, please let us know: │
│ https://github.com/kubernetes/minikube/issues/new/choose │
│ │
│ * Please run minikube logs --file=logs.txt
and attach logs.txt to the GitHub issue. │
│ │
╰─────────────────────────────────────────────────────────────────────────────────────────────╯
I0702 15:55:19.709703 2212 out.go:177]
If you run sudo systemctl status cri-docker.service
what do you get?
What Happened?
root@ip-172-31-8-53:/home/ubuntu# minikube status minikube type: Control Plane host: Stopped kubelet: Stopped apiserver: Stopped kubeconfig: Stopped
Attach the log file
root@ip-172-31-8-53:/home/ubuntu# minikube status minikube type: Control Plane host: Stopped kubelet: Stopped apiserver: Stopped kubeconfig: Stopped
Operating System
No response
Driver
No response