Running microk8s inspect displays cascade of errors after snap install on Ubuntu 25.10 #5302
Description
Summary
I wanted to switch from minikube to microk8s on my Ubuntu 25.10 machine, followed the steps in the official documentation. Then installed a helm chart that works fine in minikube and noticed that a Pod fails to resolve a hostname that is publicly available and resolves on host machine.
So I ran sudo microk8s inspect and were confronted with a list of errors indicating that the hostname resolution problem might only be a symptom of a deeper running issue.
I reinstalled microk8s and directly ran inspect after the snap install command, and same errors were show.
Possibly related to #5283 , #5266 due to sudo-rs -E ignore?
sudo microk8s version
[sudo: authenticate] Password:
MicroK8s v1.32.9 revision 8511 What Should Happen Instead?
No issues in inspect output after fresh install of microk8s on Ubuntu 25.10
Reproduction Steps
sudo snap install microk8s --classicsudo microk8s inspect
Introspection Report
warning: preserving the entire environment is not supported, -E is ignored
/snap/microk8s/8511/inspect.sh: line 7: /actions/common/utils.sh: No such file or directory
/snap/microk8s/8511/inspect.sh: line 480: exit_if_not_root: command not found
Inspecting system
Inspecting Certificates
Can't open /certs/ca.crt for reading, No such file or directory
124227737712448:error:02001002:system library:fopen:No such file or directory:../crypto/bio/bss_file.c:69:fopen('/certs/ca.crt','r')
124227737712448:error:2006D080:BIO routines:BIO_new_file:no such file:../crypto/bio/bss_file.c:76:
unable to load certificate
WARNING: This deployments certificates will expire in $days days.
Either redeploy MicroK8s or attempt a refresh with "microk8s refresh-certs"
Inspecting services
/snap/microk8s/8511/inspect.sh: line 503: is_strict: command not found
/snap/microk8s/8511/inspect.sh: line 23: is_strict: command not found
Service snap.microk8s.daemon-cluster-agent is running
/snap/microk8s/8511/inspect.sh: line 23: is_strict: command not found
Service snap.microk8s.daemon-containerd is running
/snap/microk8s/8511/inspect.sh: line 23: is_strict: command not found
Service snap.microk8s.daemon-kubelite is running
/snap/microk8s/8511/inspect.sh: line 23: is_strict: command not found
FAIL: Service snap.microk8s.daemon-flanneld is not running
For more details look at: sudo journalctl -u snap.microk8s.daemon-flanneld
/snap/microk8s/8511/inspect.sh: line 23: is_strict: command not found
FAIL: Service snap.microk8s.daemon-etcd is not running
For more details look at: sudo journalctl -u snap.microk8s.daemon-etcd
/snap/microk8s/8511/inspect.sh: line 23: is_strict: command not found
FAIL: Service snap.microk8s.daemon-apiserver-proxy is not running
For more details look at: sudo journalctl -u snap.microk8s.daemon-apiserver-proxy
/snap/microk8s/8511/inspect.sh: line 23: is_strict: command not found
Service snap.microk8s.daemon-apiserver-kicker is running
Copy service arguments to the final report tarball
cp: cannot stat '/args': No such file or directory
Inspecting AppArmor configuration
/snap/microk8s/8511/inspect.sh: line 54: is_strict: command not found
Gathering system information
Copy processes list to the final report tarball
Copy disk usage information to the final report tarball
Copy memory usage information to the final report tarball
Copy server uptime to the final report tarball
Copy openSSL information to the final report tarball
/snap/microk8s/8511/inspect.sh: line 109: is_strict: command not found
Copy snap list to the final report tarball
Copy VM name (or none) to the final report tarball
Copy current linux distribution to the final report tarball
Copy asnycio usage and limits to the final report tarball
Copy inotify max_user_instances and max_user_watches to the final report tarball
Copy network configuration to the final report tarball
/snap/microk8s/8511/inspect.sh: line 84: is_strict: command not found
Inspecting kubernetes cluster
Inspect kubernetes cluster
/snap/microk8s/8511/inspect.sh: line 137: is_strict: command not found
cp: cannot stat '/bom.json': No such file or directory
/snap/microk8s/8511/inspect.sh: line 195: is_strict: command not found
/snap/microk8s/8511/inspect.sh: line 223: is_strict: command not found
WARNING: Docker is installed.
File "/etc/docker/daemon.json" does not exist.
You should create it and add the following lines:
{
"insecure-registries" : ["localhost:32000"]
}
and then restart docker with: sudo systemctl restart docker
/snap/microk8s/8511/inspect.sh: line 291: is_strict: command not found
/snap/microk8s/8511/inspect.sh: line 311: is_strict: command not found
/snap/microk8s/8511/inspect.sh: line 325: is_strict: command not found
/snap/microk8s/8511/inspect.sh: line 369: is_strict: command not found
WARNING: Maximum number of inotify user watches is less than the recommended value of 1048576.
Increase the limit with:
echo fs.inotify.max_user_watches=1048576 | sudo tee -a /etc/sysctl.conf
sudo sysctl --system
Building the report tarball
gzip: /inspection-report-20251119_101751.tar: No such file or directory
Report tarball is at /inspection-report-20251119_101751.tar.gz
Can you suggest a fix?
Are you interested in contributing with a fix?
potentially yes, but this bug looks like a fundamental problem that might affect every Ubuntu 25.10 machine. I guess that should be fixed by an active maintainer.