microk8s: microk8s (Windows) command not found after fresh installation

Please run microk8s inspect and attach the generated tarball to this issue. --> Sorry cannot run microk8s inspect

After fresh / first installation of microk8s on Windows 10 Pro (Version 1903) with the 2.0 installer, i cannot run microk8s commands. All commands are returning:

sudo: microk8s.status: command not found An error occurred when trying to execute ‘sudo microk8s.status --wait-ready’ with ‘multipass’: returned exit code 1.

sudo: microk8s.inspect: command not found An error occurred when trying to execute ‘sudo microk8s.inspect’ with ‘multipass’: returned exit code 1.

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 25 (9 by maintainers)

Most upvoted comments

I still have this issue on windows. the network test is fine (ping to 1.1.1.1 and netcraft works)

An error occurred when trying to execute 'sudo microk8s.status --wait-ready' with 'multipass': returned exit code 1.

Just run:

multipass exec microk8s-vm -- sudo snap install microk8s --classic

and it all should start working fine.

TibebeJS on Dec 20, 2020

Trying to install microk8s snap manually ends in this:

multipass exec microk8s-vm -- sudo snap install microk8s --classic --channel=1.18/stable

error: cannot install "microk8s": persistent network error: Post https://api.snapcraft.io/v2/snaps/refresh: dial tcp: lookup api.snapcraft.io: Temporary failure in name resolution

mmattersdorfer on Jul 27, 2020

Hi everyone,

In addition to the excellent answer that fixed my issue on Windows: multipass exec microk8s-vm -- sudo snap install microk8s --classic

I had to create the personal config file by creating the MicroK8s folder and then: microk8s config > config

It seems that something is not well explained in the installation guide…

Thanks.

danifgxcom on Oct 8, 2021

Hi @joedborg ,

the firewall of my company vpn blocked the calls. I deactivted it and then the pings and installation worked. Also the microk8s commands are now working.

Thanks, Marcus

mmattersdorfer on Jul 30, 2020

Hi!

Is there any update on this? I installed yesterday on Windows 10 pro version 2004 and I’m getting the same error. Path seems to be correct.

Thanks, Daniel.

dmirandab on Jul 27, 2020