Kubernetes hangs on Start

[SCBionicle]

In reference to issue: #1962

• [ ✅ ] I have tried with the latest version of my channel (Stable)
• [ ✅ ] I have uploaded Diagnostics
• Diagnostics ID: 26F01EFE-71B3-4E04-8B54-43D240B0DA24/20200625234848

Expected behavior

Kubernetes status on Docker for Windows transitions to running and I should be able to access the context through kubectl

Actual behavior

After enabling Kubernetes in the Docker settings through the Docker Dashboard, it hangs on starting (waited for at least 10 minutes) and cannot connect to the generated context through kubectl.

Information

This bug is consistently reproducible on my machine as of the previous update and is still present today.

• Windows Version: Windows 10 Pro Update 2004 Build 19041
• Docker Desktop Version: 2.3.0.3 (46619) (Stable)
• Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM: No, this is a physical machine

Steps to reproduce the behavior

1. Open Docker Desktop Dashboard
2. Go to the settings
3. Go to Kubernetes tab
4. Enable Kubernetes
5. (No prompt appears in comparison to Mac)
6. Press "Apply & Restart"
7. Wait for restart
8. Docker starts, but Kubernetes hangs under starting indefinitely

[docker-robott]

Issues go stale after 90 days of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30 days of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

[SCBionicle]

/remove-lifecycle stale

[SCBionicle]

Still an issue in this version (latest stable release at this post date):
Client: Docker Engine - Community
Azure integration 0.1.15
Version: 19.03.12
API version: 1.40
Go version: go1.13.10
Git commit: 48a66213fe
Built: Mon Jun 22 15:43:18 2020
OS/Arch: windows/amd64
Experimental: false

Server: Docker Engine - Community
Engine:
Version: 19.03.12
API version: 1.40 (minimum version 1.12)
Go version: go1.13.10
Git commit: 48a66213fe
Built: Mon Jun 22 15:49:27 2020
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: v1.2.13
GitCommit: 7ad184331fa3e55e52b890ea95e65ba581ae3429
runc:
Version: 1.0.0-rc10
GitCommit: dc9208a3303feef5b3839f4323d9beb36df0a9dd
docker-init:
Version: 0.18.0
GitCommit: fec3683
Kubernetes:
Version: Unknown
StackAPI: Unknown

[SCBionicle]

New Diagnostic ID: 26F01EFE-71B3-4E04-8B54-43D240B0DA24/20200924011440

[docker-robott]

Issues go stale after 90 days of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30 days of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

[SCBionicle]

/remove-lifecycle stale

[docker-robott]

Issues go stale after 90 days of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30 days of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked