-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Unable to Dynamically Allocate Storage #1428
Comments
ref #1422 since the same panic is occuring here
cc @tgraf |
+1 I'm seeing the exact same issue on a similar setup. I've tested with both virtualbox and xhyve drivers. I can't seem to get minikube to see any files in a PV, whether using a manually created files on the host or through using the In short, the steps at https://kubernetes.io/docs/tasks/configure-pod-container/configure-persistent-volume-storage/ aren't working on minikube. I'm surprised more aren't reporting this given the popularity of minikube. |
Issues go stale after 90d of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
BUG REPORT
Minikube version
Environment:
What happened:
Minikube was unable to dynamically allocate storage for a pod using a PersistentVolume and a PersistentVolumeClaim.
What you expected to happen:
I expected the http-server in the pod to be able to access the index.html file that exists on the hostPath referenced in the volume (task-pv-volume).
After creating the PersistentVolume (task-pv-volume) I expected the subsequent PersistentVolumeClaim (task-pv-claim) to cause the Kubernetes control plane to match that PersistentVolume with that PersistentVolumeClaim based the claim’s requirements and cause the STATUS of the volume to be "Bound" to that claim.
How to reproduce it:
Install minikube:
Set minikube docker-env
Creating an index.html file on your Node
Creating a PersistentVolume
Creating a PersistentVolumeClaim
Creating a Pod
Install curl and run curl localhost:
Expected to see:
But this is what the curl command returned:
Anything else do we need to know:
The steps above came directly Configuring a Pod to Use a PersistentVolume for Storage documentation at https://kubernetes.io/docs/tasks/configure-pod-container/configure-persistent-volume-storage/
The only difference is that I reduced the storage sizes in task-pv-volume and task-pv-claim to ensure that the failure was not caused by lack of disk space.
The text was updated successfully, but these errors were encountered: