Microk8s installer on windows 10 failing
See original GitHub issueAfter installing the microk8s installer on my windows. I tried to configure it using --cpu 2, --mem 5G and --storage 60gb but it returns:
launch failed: The following errors occurred: microk8s-vm: timed out waiting for response
I also tried using multipass with hyper V enable but I got the same time out error.
OS: Windows 10 RAM: 8GB ROM: 500GB CORES: 4
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:8 (1 by maintainers)
Top Results From Across the Web
"microk8s install" fails on Windows 10 version 2004 #1379
"microk8s install" fails on Windows 10 with the following message: An error occurred when trying to execute 'sudo ping -c 1 snapcraft.io' with...
Read more >Troubleshooting - MicroK8s
If a pod is not behaving as expected, the first port of call should be the logs. First determine the resource identifier for...
Read more >Microk8s offline installation failed with timeout
Hi, Followed the instruction from MicroK8s - Alternative installs (MacOS/Windows 10/Multipass), with the virtual network interface.
Read more >Installing MicroK8S on Ubuntu 22.10
Interacting with snapd is not yet supported on Windows Subsystem for Linux. This command has been left available for documentation purposes only ...
Read more >How to use MicroK8s with Juju
Install and set up MicroK8s. For installation instructions for other platforms, including Windows 10, macOS, ARM devices such as Raspberry Pi and LXD,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@RFMVasconcelos thanks for your response.
Suggestion noted.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.