Unable to connect to internal registry

I followed the instructions here https://microk8s.io/docs/registry-built-in and different variations I found including 0.0.0.0 but in each case there is nothing listening / exposed on 32000

When trying to debug the previous issue I reported https://github.com/canonical/microk8s/issues/3082 I noticed the calico vxlan nic gave access to the cluster so tried tagging the image to be that so <vxlan.calico.ip>:32000/my-image and with that I was able to push successfully to the microk8s registry; however, when attempting to deploy a chart it results in an Image Pull error

Is there a recommended previous stable version of microk8s where everything is working because the latest stable version unfortunately doesn’t seem to be all that stable or perhaps the latest documentation is not in sync with the release inspection-report-20220429_173027.tar.gz

Please run microk8s inspect and attach the generated tarball to this issue.

We appreciate your feedback. Thank you for using microk8s.

[SamD]

@balchua An update on this, I decided to look at this again and it appears related to running docker in rootless mode : https://docs.docker.com/engine/security/rootless/

I switched back to standard docker engine install for Ubuntu https://docs.docker.com/engine/install/ubuntu/ and it worked fine. I’m not sure what the specifics are with the rootless setup that result in the failures, there are limitations listed on the page, but figured I would provide the update here as a heads up

[SamD]

@SamD @thebpmgroup are you both runnin microk8s on VMs?

The one i showed above is im running directly without vm.

Yes I’m running snap from now Ubuntu 22.04, I haven’t tried again since my last update here , I don’t have a lot of time to try to dig into the root cause although if I find some time over the weekend I might try again since I upgraded my distro.