[Windows] Juju.exe and MicroK8s.exe bootstrap error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Yang Kelvin Liu |
Bug Description
Hi all,
this is a follow-up from an initial discussion on Juju discourse: https:/
I’m currently writing a blog on reproducing Mark Shuttleworth demo at DockerCon 2021, but on Windows.
When trying `juju.exe bootstrap microk8s` command, with MicroK8s for Windows running as the cluster, it ends up with the following error:
```
$ juju.exe bootstrap microk8s
ERROR The microk8s user group is created during the microk8s snap installation.
Users in that group are granted access to microk8s commands and this
is needed for Juju to be able to interact with microk8s.
Add yourself to that group before trying again:
sudo usermod -a -G microk8s GHOSTNIX\corsair
```
Even if you might already know it, please note that MicroK8s for Windows creates a VM, using Multipass.exe, with the user "ubuntu".
When running the `microk8s` command, everything works fine and handles the "change" of user properly.
Thanks in advance for your help and support.
Changed in juju: | |
milestone: | none → 2.9.6 |
importance: | Undecided → High |
status: | New → Triaged |
Changed in juju: | |
milestone: | 2.9.6 → 2.9.7 |
Changed in juju: | |
status: | Triaged → In Progress |
assignee: | nobody → Yang Kelvin Liu (kelvin.liu) |
Changed in juju: | |
milestone: | 2.9.7 → 2.9.8 |
Changed in juju: | |
milestone: | 2.9.8 → 2.9.9 |
Changed in juju: | |
status: | Fix Committed → Fix Released |
Please note that the "cloud" is added by updating the `$env:KUBECONFIG` and/or saving the MicroK8s config into the `$HOME\ .kube\config` file.