new issue in travis: Insufficient permissions to access MicroK8s
See original GitHub issueour travis builds have been fine, until this morning. now we see this message:
Insufficient permissions to access MicroK8s
our install script has this, which has not changed in a while, certainly not this morning:
sudo snap install microk8s --classic
has something changed on your end? if so, what is the last version we can pin before this change was made? or was this a change on travis’s side?
of the two suggested changes, the one suggesting a usermod
and relogin clearly is not applicable to a travis scenario.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:9 (4 by maintainers)
Top Results From Across the Web
new issue in travis: Insufficient permissions to access MicroK8s
our travis builds have been fine, until this morning. now we see this message: Insufficient permissions to access MicroK8s our install ...
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 not granting me permissions to execute commands
Despite being in the microk8s OS group and having r-x access to the local config files, I am unable to execute microK8s commands...
Read more >jupyterhub/jupyterhub - Gitter
I am attempting to find documentation for jupyterhub on how to change what sort of server is spawned based on the use requesting...
Read more >Deploying microservices to Kubernetes using OpenLiberty
Insufficient permissions to access MicroK8s. You can either try again with sudo or add the user dave to the 'microk8s' group: sudo usermod...
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
@starpit you would have to use sudo then. The 1.14, 1.15 and latest tracks have been updated to require sudo (or users in the microk8s group).
Apologies for this inconvenience. We communicated this change in https://discuss.kubernetes.io/t/explicit-use-of-sudo-in-microk8s-cli/7605 but I see this announcement did not reach you. The tag you should watch for is “microk8s” (https://meta.discourse.org/t/email-notifications-based-on-questions-with-specific-tag/55691)
@tvansteenburgh @ammarn911 this has happen in the past. Some users prefer mailing lists. I know this is not the direction we are heading. I have to admit it is easier to register on a maining list than to create an account on a discourse forum and configure your profile so that you get notifications on a tag.
Insufficient permissions to access MicroK8s. You can either try again with sudo or add the user moctarjallo to the ‘microk8s’ group:
This is the output i get when i run
microk8s enable kubeflow
And when i retry it with those 2 commands i still get the same complaining after.
If i retry using
sudo
instead it says:This command can’t be run as root. Try
microk8s enable kubeflow
instead.What is the solution? This is the first time i’m installing kubeflow on my machine and i don’t have kubernetes or docker installed. I am using ubuntu 20.04