[Question] Got "Permission denied" in successful attached volume #1713
Labels
kind/question
Please use `discussion` to ask questions instead
Comments
manhhailua
added
the
kind/question
|
|
@joshimoo I updated this reply after successfully access the mount |
|
@manhhailua , I think the issue is 'There's no available disk for replica pvc-dc8a0fc4-0483-474c-96b7-84ee14781fe7-r-b632a64f, size 2147483648'. You might need to enable the |
|
@boknowswiki I upgraded longhorn release with |
|
FYI, I stuck with a similar issue after installing bitnami/redis using longhorn on k8s. By including |
|
I'm facing a similar issue on the Prometheus Helm Chart. Provisioning was through Longhorn Auto provisioning, but Prometheus Pods are crashing due to permission issues. I wonder if there's also a parameter for Prometheus to make it working. |
Same here. I did a dirty workaround by scaling the deployment to 0, attaching the volume via the GUI to a node, mounting it the volume on the node to /mnt and then just chowning /mnt to the specific user 65534:65534. After that unmount that volume and scale the deploy to 1. You can find the device-mapper Endpoint in the UI when clicking on the pvc. It should be under /dev/longhorn/. |
|
I am currently having the same issue. I deployed Longhorn using the Helm chart on a 3 node Microk8s cluster composed of 3 Ubuntu servers. open-iscsi is installed on all nodes. When I deploy either Grafana or Postgres to the cluster with the Longhorn storage class, the pods fail with permission denied errors. I followed this guide for my install: https://github.com/balchua/do-microk8s/blob/master/docs/longhorn.md Edit: I managed to solve the issue by adding a "securityContext" section to my pod specification. Here's the .yml for Grafana: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I got error "permission denied" in all pods which is using longhorn volumes on a k3s cluster with 1 master and 2 nodes (all those threes are ubuntu 18.04 on AWS and having Security Groups rules follow k3s network config requirements).
Redis pod log:
Postgresql pod log:
I installed the k3s server with:
And installed longhorn by
helm:I did try using
securityContextbut no luck:The text was updated successfully, but these errors were encountered: