Closed montmejat closed 2 years ago
Update: this seems to come from the minikube mount
command and from the shared folders, if I copy the files directly into minikube, I do not get this error of corrupted files.
/kind support
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
I have the same issue as @aurelien-m :
Hi @aurelien-m, this should have been fixed with https://github.com/kubernetes/minikube/pull/13013, try using the newest version of minikube (v1.24.0) and let me know if it's resolved, thanks!
Hi @guiliguili, I see you're using the newest version of minikube and still seem to be getting this error. What driver do you use with minikube? And have you tried deleting the cluster (minikube delete --all
) and creating a new one since updating to minikube v1.24.0?
Thank you for coming back, I cannot test it as I have moved away from using Kubernetes and minikube at the moment, and I don't have access to my older work on it!
@aurelien-m should we close this issue if no further queries?
I'm fine with closing it, I don't have any further queries
/close
@RA489: Closing this issue.
logs_alsologtostderr.txt
Steps to reproduce the issue:
ls: cannot access '/data': Input/output error
Full output of
minikube logs
command:I've added the logs with
--alsologtostderr
as a file because it is too big.Does any one has an idea where it could come from? It seems to work fine at first, I can access the files in minikube and in my applications. Then, I don't touch it for a few minutes and then it gets corrupted. I can't seem to find what the cause is, if anyone has had a similar problem, I would appreciate any information that could help me. What could be a procedure that I can follow to debug an error like this? Is there any bad practice from my docker image using that volume that could break it (it's a rather simple app)?