This message was deleted.
# k3d
a
This message was deleted.
w
I didn't see any issues with that yet. The mount itself seems to work somewhat, otherwise the cluster wouldn't start. Anyway, what do you see in the
kubectl describe pvc
and
kubectl describe pv
outputs? I assume you want to use the local-path provisioner?
f
I'll have to double check with the windows folks, but we were trying to deploy a postgres container and it did not like the volume.
Seems like the pvc is not being created due to permissions issues on the directory in question
@wide-garage-9465 Is there a way to specify the UID used by the local-path-provisioner (or k3d itself)?
w
In the volume binds of k3d you can use the docker volume modifiers, but I guess that wouldn't help you here. You can customize the provisioner as described here: https://github.com/rancher/local-path-provisioner#configuration
f
I guess I could modify that configmap setup: section to have a chown?
w
I'd assume so. It has a
chmod
in the end already.
104 Views