https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rancher-desktop
a
This message was deleted.
f
hostpath
is not a storage class, but a volume type. Rancher Desktop provides a 
local-path
storage class, that is a 
local
volume.
b
same question remains then - why is the error thrown?
i'm not getting this error in minikube
f
Maybe minikube has a 
hostpath
storage class? Which would be a confusing name choice...
Let me see if I can spin up minikube to double-check
b
no, it must be a deficiency with k3s 😞
man, you would think that local-path would be installed as hostpath so there was a graceful fallback
f
Well, show your volume definitions; I suspect you specify 
hostpath
as a storage class name, which is not defined under 
k3s
b
I do not
Copy code
volumes:
- name: foobar
  hostPath:
    path: "/tmp/foobar"
it's a built in, so no need
like emptyDir
f
It is not called 
hostpath
on 
minikube
either; it is called 
default
there:
Copy code
$ kubectl get sc
NAME                 PROVISIONER                RECLAIMPOLICY   VOLUMEBINDINGMODE   ALLOWVOLUMEEXPANSION   AGE
standard (default)   <http://k8s.io/minikube-hostpath|k8s.io/minikube-hostpath>   Delete          Immediate           false                  27s
b
🤷
f
So you need to show an example config that can reproduce the error, if you want some help with finding your problem
b
i just did. right above?
lol
f
That is not a complete example that you can pass to 
kubectl apply ...
b
don't worry about it 😉
f
ok then
b
cool. very mature.
thanks man.
f
I've added a working example to your "bug" report. It is a problem with your config. If you are not willing to share it, then there is nothing else I can do to help you.
b
what ever you say man. if you think this is the way to increase adoption
f
Sorry, what do you expect me to do? I genuinely have no idea.
You show an error message with an incomplete sample snippet that doesn't reproduce the issue when added to a full pod spec.
b
it's fine. i was the last rancher hold out. i'm just gonna move to minikube. every one on my team can run this chart with success locally
thanks
Which would be a confusing name choice...
I believe this is the "cause". They chose to name their pvc solution the same thing you would use for an ephemeral volume. You deserve an apology. I'm sorry.
f
It's ok. I'm trying to help, but you seemed in a bad mood...
4 Views
Open in Slack
PreviousNext
Powered by