Kubernetes cannot be started

catkeeper1 commented 1 year ago

Description

After I turn on Kubernetes in setting menu and wait for a while, it was shown that Kubernetes cannot be started(status light in the left bottom conner is red)

I can run "docker run hello-world" successfully. It prove the docker is running and it can pull images.

When I run "docker images", there is no image about k8s are downloaded. Only the hello-world image is downloaded: REPOSITORY TAG IMAGE ID CREATED SIZE hello-world latest 9c7a54a9a43c 3 months ago 13.3kB

After I run self checking tool, I got: 1 : The test: are the backend processes running? Failed with: 1 error occurred: vpnkit.exe is not running

Not all of the backend processes are running.

2 : The test: is the VM networking working? Failed with: network checks failed: failed to ping host: exit status 1

VM seems to have a network connectivity issue. Please check your host firewall and anti-virus settings in case they are blocking the VM.

If I run "kubectl get nodes", it return "Unable to connect to the server: EOF".

When I try to upload diagnosis report to gen a diagnosis ID, I got: Cannot upload diagnostics. Reason: Error invoking remote method 'desktop-go-backend': [object Object] So, I did not have a diagnosis ID for this issue now.

Reproduce

Install docker desktop and turn on kubernates feature in setting menu.

Expected behavior

Kubernates can be started succesfully. I can run "kubectl get nodes"

docker version

Client:
Cloud integration: v1.0.29
Version:           20.10.17
API version:       1.41
Go version:        go1.17.11
Git commit:        100c701
Built:             Mon Jun  6 23:09:02 2022
OS/Arch:           windows/amd64
Context:           default
Experimental:      true

Server: Docker Desktop 4.12.0 (85629)
Engine:
  Version:          20.10.17
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.17.11
  Git commit:       a89b842
  Built:            Mon Jun  6 23:01:23 2022
  OS/Arch:          linux/amd64
  Experimental:     false
containerd:
  Version:          1.6.8
  GitCommit:        9cd3357b7fd7218e4aec3eae239db1f68a5a6ec6
runc:
  Version:          1.1.4
  GitCommit:        v1.1.4-0-g5fd4c4d
docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

docker info

Client:
Context:    default
Debug Mode: false
Plugins:
  buildx: Docker Buildx (Docker Inc., v0.9.1)
  compose: Docker Compose (Docker Inc., v2.10.2)
  extension: Manages Docker extensions (Docker Inc., v0.2.9)
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc., 0.6.0)
  scan: Docker Scan (Docker Inc., v0.19.0)

Server:
Containers: 1
  Running: 0
  Paused: 0
  Stopped: 1
Images: 1
Server Version: 20.10.17
Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
  userxattr: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 2
Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 9cd3357b7fd7218e4aec3eae239db1f68a5a6ec6
runc version: v1.1.4-0-g5fd4c4d
init version: de40ad0
Security Options:
 seccomp
   Profile: default
  cgroupns
Kernel Version: 5.10.124-linuxkit
Operating System: Docker Desktop
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 8.746GiB
Name: docker-desktop
ID: EPBX:G3TZ:TBFS:VSK4:ATCM:ZMIC:GUYK:M66O:D3HA:YXYR:PW5Y:7SUZ
Docker Root Dir: /var/lib/docker
Debug Mode: false
HTTP Proxy: http.docker.internal:3128
HTTPS Proxy: http.docker.internal:3128
No Proxy: hubproxy.docker.internal
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
  hubproxy.docker.internal:5000
  127.0.0.0/8
Live Restore Enabled: false

Diagnostics ID

fail to generate diagnosis ID

Additional Info

No response

catkeeper1 commented 1 year ago

I suspect some security software(such as firewall) block something in my laptop so that is does not work. However, I did not have the access right to turn off those software since it is controlled by admin. Is there anything I can do to prove this is blocked by security software so that I can bring those evidence to security admin team and ask them to do something?

bsousaa commented 1 year ago

it very much sounds you are having networking issues. Do you have connectivity issues with other services/tools?

docker / for-win