Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Minikube 1.2.0 driver=none output not user-friendly #4615

Closed
staticdev opened this issue Jun 27, 2019 · 5 comments
Closed

Minikube 1.2.0 driver=none output not user-friendly #4615

staticdev opened this issue Jun 27, 2019 · 5 comments

Comments

@staticdev
Copy link
Contributor

staticdev commented Jun 27, 2019

The exact command to reproduce the issue: minikube start --vm-driver=none

The full output of the command that failed: 😄 minikube v1.2.0 on linux (amd64)
🔥 Creating none VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...
🐳 Configuring environment for Kubernetes v1.15.0 on Docker
▪ kubelet.resolv-conf=/run/systemd/resolve/resolv.conf
💾 Downloading kubeadm v1.15.0
💾 Downloading kubelet v1.15.0

💣 Failed to update cluster: downloading binaries: copying kubeadm: copy: error creating file at /usr/bin/kubeadm: open /usr/bin/kubeadm: permission denied

😿 Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
👉 https://github.com/kubernetes/minikube/issues/new

The output of the minikube logs command:

E0626 21:02:07.466094   28917 logs.go:155] Failed to list containers for "kube-apiserver": running command: docker ps -a --filter="name=kube-apiserver" --format="{{.ID}}"
 output: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.39/containers/json?all=1&filters=%7B%22name%22%3A%7B%22kube-apiserver%22%3Atrue%7D%7D: dial unix /var/run/docker.sock: connect: permission denied
: running command: docker ps -a --filter="name=kube-apiserver" --format="{{.ID}}"
.: exit status 1
E0626 21:02:07.501122   28917 logs.go:155] Failed to list containers for "coredns": running command: docker ps -a --filter="name=coredns" --format="{{.ID}}"
 output: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.39/containers/json?all=1&filters=%7B%22name%22%3A%7B%22coredns%22%3Atrue%7D%7D: dial unix /var/run/docker.sock: connect: permission denied
: running command: docker ps -a --filter="name=coredns" --format="{{.ID}}"
.: exit status 1
E0626 21:02:07.535047   28917 logs.go:155] Failed to list containers for "kube-scheduler": running command: docker ps -a --filter="name=kube-scheduler" --format="{{.ID}}"
 output: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.39/containers/json?all=1&filters=%7B%22name%22%3A%7B%22kube-scheduler%22%3Atrue%7D%7D: dial unix /var/run/docker.sock: connect: permission denied
: running command: docker ps -a --filter="name=kube-scheduler" --format="{{.ID}}"
.: exit status 1
E0626 21:02:07.569985   28917 logs.go:155] Failed to list containers for "kube-proxy": running command: docker ps -a --filter="name=kube-proxy" --format="{{.ID}}"
 output: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.39/containers/json?all=1&filters=%7B%22name%22%3A%7B%22kube-proxy%22%3Atrue%7D%7D: dial unix /var/run/docker.sock: connect: permission denied
: running command: docker ps -a --filter="name=kube-proxy" --format="{{.ID}}"
.: exit status 1
E0626 21:02:07.603184   28917 logs.go:155] Failed to list containers for "kube-addon-manager": running command: docker ps -a --filter="name=kube-addon-manager" --format="{{.ID}}"
 output: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.39/containers/json?all=1&filters=%7B%22name%22%3A%7B%22kube-addon-manager%22%3Atrue%7D%7D: dial unix /var/run/docker.sock: connect: permission denied
: running command: docker ps -a --filter="name=kube-addon-manager" --format="{{.ID}}"
.: exit status 1
E0626 21:02:07.636444   28917 logs.go:155] Failed to list containers for "kubernetes-dashboard": running command: docker ps -a --filter="name=kubernetes-dashboard" --format="{{.ID}}"
 output: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.39/containers/json?all=1&filters=%7B%22name%22%3A%7B%22kubernetes-dashboard%22%3Atrue%7D%7D: dial unix /var/run/docker.sock: connect: permission denied
: running command: docker ps -a --filter="name=kubernetes-dashboard" --format="{{.ID}}"
.: exit status 1
E0626 21:02:07.670054   28917 logs.go:155] Failed to list containers for "storage-provisioner": running command: docker ps -a --filter="name=storage-provisioner" --format="{{.ID}}"
 output: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.39/containers/json?all=1&filters=%7B%22name%22%3A%7B%22storage-provisioner%22%3Atrue%7D%7D: dial unix /var/run/docker.sock: connect: permission denied
: running command: docker ps -a --filter="name=storage-provisioner" --format="{{.ID}}"
.: exit status 1
==> dmesg <==
[  +0,130196] platform MSFT0101:00: failed to claim resource 1: [mem 0xfed40000-0xfed40fff]
[  +0,000004] acpi MSFT0101:00: platform device creation failed: -16
[  +0,840212] usb: port power management may be unreliable
[  +0,008586] platform eisa.0: EISA: Cannot allocate resource for mainboard
[  +0,000001] platform eisa.0: Cannot allocate resource for EISA slot 1
[  +0,000001] platform eisa.0: Cannot allocate resource for EISA slot 2
[  +0,000001] platform eisa.0: Cannot allocate resource for EISA slot 3
[  +0,000001] platform eisa.0: Cannot allocate resource for EISA slot 4
[  +0,000001] platform eisa.0: Cannot allocate resource for EISA slot 5
[  +0,000001] platform eisa.0: Cannot allocate resource for EISA slot 6
[  +0,000000] platform eisa.0: Cannot allocate resource for EISA slot 7
[  +0,000001] platform eisa.0: Cannot allocate resource for EISA slot 8
[  +0,034239] atkbd serio0: Unknown key released (translated set 2, code 0x7c on isa0060/serio0).
[  +0,000002] atkbd serio0: Use 'setkeycodes 7c <keycode>' to make it known.
[  +0,014524] Couldn't get size: 0x800000000000000e
[  +0,153324] acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
[  +0,035536] atkbd serio0: Unknown key released (translated set 2, code 0x7c on isa0060/serio0).
[  +0,000003] atkbd serio0: Use 'setkeycodes 7c <keycode>' to make it known.
[  +0,023124] i2c_hid i2c-ITE8350:00: i2c-ITE8350:00 supply vdd not found, using dummy regulator
[  +0,000023] i2c_hid i2c-ITE8350:00: i2c-ITE8350:00 supply vddl not found, using dummy regulator
[  +0,051130] i2c_hid i2c-MSFT0001:00: i2c-MSFT0001:00 supply vdd not found, using dummy regulator
[  +0,000015] i2c_hid i2c-MSFT0001:00: i2c-MSFT0001:00 supply vddl not found, using dummy regulator
[  +0,130110] atkbd serio0: Unknown key released (translated set 2, code 0x7c on isa0060/serio0).
[  +0,000001] atkbd serio0: Use 'setkeycodes 7c <keycode>' to make it known.
[  +0,203962] atkbd serio0: Unknown key released (translated set 2, code 0x7c on isa0060/serio0).
[  +0,000001] atkbd serio0: Use 'setkeycodes 7c <keycode>' to make it known.
[  +0,618460] atkbd serio0: Unknown key released (translated set 2, code 0x7c on isa0060/serio0).
[  +0,000002] atkbd serio0: Use 'setkeycodes 7c <keycode>' to make it known.
[  +0,202365] atkbd serio0: Unknown key released (translated set 2, code 0x7c on isa0060/serio0).
[  +0,000002] atkbd serio0: Use 'setkeycodes 7c <keycode>' to make it known.
[  +1,600817] uvcvideo 1-7:1.0: Entity type for entity Extension 4 was not initialized!
[  +0,000003] uvcvideo 1-7:1.0: Entity type for entity Extension 3 was not initialized!
[  +0,000001] uvcvideo 1-7:1.0: Entity type for entity Processing 2 was not initialized!
[  +0,000002] uvcvideo 1-7:1.0: Entity type for entity Camera 1 was not initialized!
[  +0,420493] ath10k_pci 0000:01:00.0: unsupported HTC service id: 1536
[  +2,809289] ath10k_pci 0000:01:00.0: unsupported HTC service id: 1536
[  +5,825351] PKCS#7 signature not signed with a trusted key
[  +0,000010] vboxdrv: loading out-of-tree module taints kernel.
[  +0,057157] PKCS#7 signature not signed with a trusted key
[  +0,000840] VBoxNetFlt: Successfully started.
[  +0,020507] PKCS#7 signature not signed with a trusted key
[  +0,001778] VBoxNetAdp: Successfully started.
[  +0,014385] PKCS#7 signature not signed with a trusted key
[  +0,000512] VBoxPciLinuxInit
[  +0,215649] kauditd_printk_skb: 36 callbacks suppressed
[jun26 20:26] test1
[  +0,000002] test2
[  +0,687483] VBoxPciLinuxLinuxUnload
[jun26 20:34] kauditd_printk_skb: 1 callbacks suppressed
[ +30,173124] L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/l1tf.html for details.

==> kernel <==
 21:02:07 up 38 min,  2 users,  load average: 0,39, 0,46, 0,53
Linux static-Aspire-R5-471T 5.0.0-17-generic #18-Ubuntu SMP Tue Jun 4 15:34:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

==> kubelet <==
-- Logs begin at Sat 2018-04-28 17:18:10 -03, end at Wed 2019-06-26 21:02:07 -03. --
-- No entries --

The operating system version: Ubuntu 19.04

Comments:

@staticdev staticdev changed the title Minikube driver=none output not user-friendly Minikube 1.2.0 driver=none output not user-friendly Jun 27, 2019
@medyagh
Copy link
Member

medyagh commented Jun 27, 2019

Thank you for creating this issue, I believe we recently merged a PR that sugests user to run it with sudo. I think it will be in the next release.

@afbjorklund
Copy link
Collaborator

First issue is #4462

@medyagh
Copy link
Member

medyagh commented Jul 2, 2019

closing in favor of #4615

@medyagh medyagh closed this as completed Jul 2, 2019
@mozai
Copy link

mozai commented Jul 17, 2019

When I do sudo minikube start it insists "⚠️ Please don't run minikube as root or with 'sudo' privileges. It isn't necessary." But when I try to launch it without root or sudo privileges, I get "💣 Failed to update cluster: downloading binaries: copying kubeadm: copy: error removing file /usr/bin/kubeadm: remove /usr/bin/kubeadm: permission denied"

@afbjorklund
Copy link
Collaborator

Sounds like a bug, it should only copy those files for the none driver (which is not supposed to warn)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants