microk8s: Failed to enable kubeflow

inspection-report-20200211_171636.tar.gz

  • Error Message:
$ microk8s.enable kubeflow
Enabling dns...
Enabling storage...
Enabling dashboard...
Enabling ingress...
Enabling rbac...
Enabling juju...
Kubeflow could not be enabled:
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--     0
 22  116M   22 25.8M    0     0  51231      0  0:39:39  0:08:48  0:30:51 71301
curl: (18) transfer closed with 94828385 bytes remaining to read

Command '('microk8s-enable.wrapper', 'juju')' returned non-zero exit status 1
Failed to enable kubeflow
  • microk8s version:
$ sudo snap find microk8s
Name      Version  Publisher   Notes    Summary
microk8s  v1.17.2  canonical✓  classic  Kubernetes for workstations and appliances

Maybe this issue is same as #943 but I’m a microk8s newbie and cannot make a correct judgement about it.

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 72 (31 by maintainers)

Most upvoted comments

You could snap install juju and then cp /snap/juju/current/bin/juju /var/snap/microk8s/current/bin/. Note this is a hack.

@SpudAldridge, @rickyking: I believe #1099 will fix the issue you’re running into. That’s available on edge now (sudo snap switch microk8s --channel edge && sudo snap refresh), or will be available on stable in a few days via #1104.

https://github.com/ubuntu/microk8s/issues/943#issuecomment-581424578

suggested

microk8s.disable kubeflow
microk8s.enable kubeflow

but that did not help

I think all of the issues in this thread have been resolved. If not, feel free to open up a new issue

@knkski Thanks. Was actually referring to post from @atamahjoubfar on Jun 10th. i got the same error. Will continue to check further when i get time and post any updates in the new issue you have created

@zshenkle: For future reference, you can enable more verbose logging like this:

KUBEFLOW_DEBUG=true microk8s.enable kubeflow

As far as the nameserver issue you ran into, I’m not sure why you would have to edit those in. Did you put those in /etc/resolv.conf on the system that you installed microk8s onto? I haven’t encountered that issue, but we’ve got some relevant documentation here that might need to call that out if it’s broadly necessary:

https://microk8s.io/docs/addon-dns

cc @ktsakalozos ^^

@sygin123: I haven’t seen that error before. Can you create a new issue in this repository, and include the output from KUBEFLOW_DEBUG=true microk8s.enable kubeflow? And are you running microk8s inside of a VM or somewhere without a lot of disk space? It looks like you may be running into an issue with disk space.

@knkski I am not running inside VM. I think you are right, my laptop does not have much space for /home. After extend the space, this issue is gone! Thanks!

@egkiastas: Can you download https://launchpad.net/juju/2.7/2.7.3/+download/juju-2.7.3-k8s.tar.xz, and place the unzipped juju binary at /var/snap/microk8s/current/bin/juju, then run these commands, and try again?

https://github.com/ubuntu/microk8s/blob/0ebbaed/snap/hooks/configure#L378-L385

#989 will fix the issue you’re running into by including the juju binary in the snap instead of downloading it. If you’d like to try that instead of the above, you should be able to by switching microk8s to the latest/edge channel (sudo snap switch microk8s --channel latest/edge && sudo snap refresh).

@ktsakalozos This also works to enable juju. But when I then try to enable Kubeflow, it gives me the following message.

Enabling dns...
Enabling storage...
Enabling dashboard...
Enabling ingress...
Enabling rbac...
Enabling juju...
Deploying Kubeflow...
Kubeflow could not be enabled:
ERROR cannot load ssh client keys: mkdir /var/snap/microk8s/1173/juju/share: permission denied

Command '('microk8s-juju.wrapper', 'bootstrap', 'microk8s', 'uk8s')' returned non-zero exit status 2
Failed to enable kubeflow

@grebennikov could you help me reproduce this? When you say “it only affects ubuntu desktop” what do you mean?

If you sudo snap remove microk8s and reinstall it with sudo snap install microk8s --classic does the problem persist? Does the microk8s.reset have any effect? Thanks.