minikube: ChromeOS compatability (mount: /sys: permission denied.: container exited unexpectedly)

At master:

./out/minikube start --vm-driver=docker
😄  minikube v1.7.0-beta.1 on Debian 9.11
✨  Selecting experimental 'docker' driver from user configuration (alternates: [none])
🔥  Creating Kubernetes in docker container with (CPUs=2), Memory=2000MB (6638MB available) ...

💣  Unable to start VM. Please investigate and run 'minikube delete' if possible: create: creating: prepare kic ssh: apply authorized_keys file ownership, output 
** stderr ** 
Error response from daemon: Container dc8e0447bd40351034d19959e58f9ae2b735e9f45110f2dbae4552a8e8d91157 is not running

** /stderr **: chown docker:docker /home/docker/.ssh/authorized_keys: exit status 1
stdout:

stderr:
Error response from daemon: Container dc8e0447bd40351034d19959e58f9ae2b735e9f45110f2dbae4552a8e8d91157 is not running

Looking at the container logs:

$ docker ps -a
CONTAINER ID        IMAGE                                COMMAND                  CREATED             STATUS                      PORTS               NAMES
dc8e0447bd40        gcr.io/k8s-minikube/kicbase:v0.0.2   "/usr/local/bin/entr…"   2 minutes ago       ...

$ docker logs dc8e0447bd40
WARN: /dev/kmsg does not exist, symlinking /dev/console
INFO: ensuring we can execute /bin/mount even with userns-remap
INFO: remounting /sys read-only
mount: /sys: permission denied.

About this issue

Original URL
State: open
Created 4 years ago
Comments: 20 (7 by maintainers)

Links to this issue

Most upvoted comments

I’ve just switched my work machine to a Pixelbook Go, so I felt I should update this issue with the latest output on the current kernel release:

Linux penguin 5.4.67-09356-gf3ed4c0c4a31 #1 SMP PREEMPT Sun Sep 27 20:35:52 PDT 2020 x86_64 GNU/Linux

😄  minikube v1.16.0 on Debian 10.5
✨  Using the docker driver based on existing profile
💨  For improved Docker performance, enable the overlay Linux kernel module using 'modprobe overlay'
❗  docker is currently using the btrfs storage driver, consider switching to overlay2 for better performance
👍  Starting control plane node minikube in cluster minikube
🚜  Pulling base image ...
🔥  Creating docker container (CPUs=2, Memory=3600MB) ...
✋  Stopping node "minikube"  ...
🔥  Deleting "minikube" in docker ...
🤦  StartHost failed, but will try again: creating host: create: creating: create kic node: container name "minikube": log: 2021-01-05T17:43:30.446193388Z  + echo 'INFO: remounting /sys read-only'
2021-01-05T17:43:30.446210943Z  INFO: remounting /sys read-only
2021-01-05T17:43:30.446240749Z  + mount -o remount,ro /sys
2021-01-05T17:43:30.457168392Z  mount: /sys: permission denied.: container exited unexpectedly
🔥  Creating docker container (CPUs=2, Memory=3600MB) ...
😿  Failed to start docker container. Running "minikube delete" may fix it: creating host: create: creating: create kic node: container name "minikube": log: 2021-01-05T17:44:32.940820072Z  + echo 'INFO: remounting /sys read-only'
2021-01-05T17:44:32.940831797Z  INFO: remounting /sys read-only
2021-01-05T17:44:32.940841973Z  + mount -o remount,ro /sys
2021-01-05T17:44:32.940849359Z  mount: /sys: permission denied.: container exited unexpectedly

💢  The minikube docker container exited unexpectedly.
💡  If you are still interested to make docker driver work. The following suggestions might help you get passed this issue:

        - Prune unused docker images, volumes, networks and abandoned containers.

                                docker system prune --volumes

        - Restart your docker service

        - Delete and recreate minikube cluster
                minikube delete
                minikube start --driver=docker

❌  Exiting due to GUEST_PROVISION: Failed to start host: creating host: create: creating: create kic node: container name "minikube": log: 2021-01-05T17:44:32.940820072Z  + echo 'INFO: remounting /sys read-only'
2021-01-05T17:44:32.940831797Z  INFO: remounting /sys read-only
2021-01-05T17:44:32.940841973Z  + mount -o remount,ro /sys
2021-01-05T17:44:32.940849359Z  mount: /sys: permission denied.: container exited unexpectedly

tstromberg on Jan 5, 2021

any news on this?

rckgomz on Apr 2, 2021

Hey @eddyjlhaigh this is on our roadmap, but we are waiting for the overlayfs kernel module to be enabled on ChromeOS. Once that module is enabled, minikube should be able to run, but I’m not sure when that can be expected to happen. Regardless, this is definitely on our radar.

priyawadhwa on Feb 24, 2021