minikube: Minikube --mount Bad file descriptor
Steps to reproduce the issue:
- The issue is happened when we install new minikube (Tested a few times)
- Older version which run a few month ago has no issue, accidentally delete old minikube image (minikube delete) that cause minikube start -> rebuild the minikube image (IP 192.168.49.2) -> issue appears.
š minikube v1.20.0 on Ubuntu 20.04 āØ Using the docker driver based on existing profile š Starting control plane node minikube in cluster minikube š Pulling base image ā¦ š Restarting existing docker container for āminikubeā ā¦ š³ Preparing Kubernetes v1.20.2 on Docker 20.10.6 ā¦ š Verifying Kubernetes componentsā¦ āŖ Using image gcr.io/k8s-minikube/storage-provisioner:v5 āŖ Using image kubernetesui/dashboard:v2.1.0 āŖ Using image kubernetesui/metrics-scraper:v1.0.4 š Enabled addons: storage-provisioner, default-storageclass, dashboard š Done! kubectl is now configured to use āminikubeā cluster and ādefaultā namespace by default
- issues appear in the mount
root@minikube:/containerfile# ls ls: cannot access ādockerā: Bad file descriptor ls: cannot access ācomposer.lockā: Bad file descriptor ls: cannot access āphpunit.xmlā: Bad file descriptor ls: cannot access āpackage-lock.jsonā: Bad file descriptor ls: cannot access āappā: Bad file descriptor ls: cannot access āwebpack.mix.jsā: Bad file descriptor ls: cannot access āfrontendā: Bad file descriptor ls: cannot access ābootstrapā: Bad file descriptor ls: cannot access ādocker-compose.ymlā: Bad file descriptor ls: cannot access ānode_modulesā: Bad file descriptor ls: cannot access āpublicā: Bad file descriptor
since they canāt access and in the pod.
/var/www/html # ls ls: ./docker: Bad file descriptor ls: ./composer.lock: Bad file descriptor ls: ./namtest10: Bad file descriptor ls: ./phpunit.xml: Bad file descriptor ls: ./package-lock.json: Bad file descriptor ls: ./app: Bad file descriptor ls: ./webpack.mix.js: Bad file descriptor ls: ./frontend: Bad file descriptor ls: ./bootstrap: Bad file descriptor ls: ./docker-compose.yml: Bad file descriptor ls: ./node_modules: Bad file descriptor ls: ./public: Bad file descriptor ls: ./database: Bad file descriptor ls: ./tests: Bad file descriptor ls: ./package.json: Bad file descriptor ls: ./vendor: Bad file descriptor ls: ./routes: Bad file descriptor ls: ./artisan: Bad file descriptor ls: ./resources: Bad file descriptor ls: ./composer.json: Bad file descriptor ls: ./server.php: Bad file descriptor ls: ./README.md: Bad file descriptor
Full output of minikube logs command:
root@minikube:~# date
Tue Aug 17 21:04:58 UTC 2021
Aug 17 20:53:53 minikube kubelet[1008]: W0817 20:53:53.347979 1008 docker_sandbox.go:402] failed to read pod IP from plugin/docker: Couldnāt find network status for test/main-page-5f47c6db5b-b76tw through plugin: invalid network status for Aug 17 20:53:54 minikube kubelet[1008]: W0817 20:53:54.692472 1008 docker_sandbox.go:402] failed to read pod IP from plugin/docker: Couldnāt find network status for test/main-page-5f47c6db5b-b76tw through plugin: invalid network status for Aug 17 20:53:58 minikube kubelet[1008]: W0817 20:53:58.400456 1008 docker_sandbox.go:402] failed to read pod IP from plugin/docker: Couldnāt find network status for test/main-page-5f47c6db5b-b76tw through plugin: invalid network status for Aug 17 20:54:02 minikube kubelet[1008]: W0817 20:54:02.092122 1008 docker_sandbox.go:402] failed to read pod IP from plugin/docker: Couldnāt find network status for test/main-page-5f47c6db5b-b76tw through plugin: invalid network status for Aug 17 20:54:03 minikube kubelet[1008]: W0817 20:54:03.309024 1008 docker_sandbox.go:402] failed to read pod IP from plugin/docker: Couldnāt find network status for test/main-page-5f47c6db5b-b76tw through plugin: invalid network status for
- Tried to build virtualbox nested (same issue)
- Tried to build Physical Server (Same issue)
- The working one for a few month (after delete old image minikube 1.20.0 ) -> it rebuild the image 192.168.49.2 -> same issue
- The Drive= virtualbox is working but the performance is slow (because it used virtualbox instead)
Anyone please know how to fix please help. I suspect the newer minikube docker image has problem with the privilege access.
Thankss
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 19 (5 by maintainers)
Commits related to this issue
- Introduce a new http -> pipelines -> blackhole soak This commit introduces a new soak to investigate our pipelines in an ongoing basis. The pipeline configuration for vector and the sample data was c... — committed to vectordotdev/vector by blt 3 years ago
- Introduce a new http -> pipelines -> blackhole soak This commit introduces a new soak to investigate our pipelines in an ongoing basis. The pipeline configuration for vector and the sample data was c... — committed to vectordotdev/vector by blt 3 years ago
- chore: Introduce a new http -> pipelines -> blackhole soak (#10142) * Introduce a new http -> pipelines -> blackhole soak This commit introduces a new soak to investigate our pipelines in an ongoi... — committed to vectordotdev/vector by blt 3 years ago
This should be fixed with the above PR, feel free to try it out with the following binaries: https://storage.googleapis.com/minikube-builds/13013/minikube-linux-amd64 https://storage.googleapis.com/minikube-builds/13013/minikube-darwin-amd64 https://storage.googleapis.com/minikube-builds/13013/minikube-windows-amd64.exe
I reinstalled the minikube in the VM and each deployment. I deleted so it is fresh deployment and the issue appeared in all new deployment docker driver.
The work around solution is change driver to VM mode so minikube will run docker in the virtual box instead of direct docker in the host. It has slower performance but it works.
Before change driver to vm mode, you try to delete all as above guide whether new minikube image is fixed or not. Till now, issue is not fixed then google, minukube virtualbox driver. This is my workaround.
On Mon, 27 Sep 2021, 07:20 Nestor Figliuolo, @.***> wrote: