This message was deleted.
# rancher-desktop
a
This message was deleted.
f
Check the size of the data volume from inside the VM:
Copy code
$ rdctl shell sudo df -h | grep /mnt/data
                         97.9G      1.6G     91.3G   2% /mnt/data
If it didn't work, then you can attempt to increase the size of the disk without the factory reset: https://rancher-users.slack.com/archives/C0200L1N1MM/p1683820729542349?thread_ts=1683820236.499459&cid=C0200L1N1MM
You must stop Rancher Desktop before resizing the disk. After resizing and restart Rancher Desktop should automatically grow the partition and make the additional space available.
Never attempt to shrink the data file; it will break the volume.
p
rdctl shell sudo df -h | grep /mnt/data
shows:
Copy code
97.9G      3.6G     89.3G   4% /mnt/data
Running that command worked however the PVCs are still stuck pending
Is it fair to say that the overrides file not picking up the disk size change is a bug?
It appears that maybe the reason they are stuck pending is that rancher only supports ReadWriteOnce access mode
f
I don't get what you are saying. Did the volume size increase or not?
p
It worked, it then appeared they were still pending b/c of the access mode and no longer the lack of space
f
And I don't know if
ReadWriteOnce
is an issue; I thought it means it can only be mounted writable by one node, not pod/container, and Rancher Desktop only uses a single node right now.
p
The access mode was RWX which isn't supported
f
I don't know what you mean by
RWX
, but using
ReadWriteOnce
should just make sure all pods needing access to the PVC will be scheduled on the same node, so that should not be your problem.
p
I think you misread my earlier message. I said that it appears Rancher only supports ReadWriteOnce. I'm not having a problem with ReadWriteOnce. The problem was the pvcs were RWX == ReadWriteMany
f
Ah, ok, so everything is good now after you switched to
ReadWriteOnce
? The PVCs are provisioned via https://github.com/rancher/local-path-provisioner, so they are backed by node filesystem storage, which obviously couldn't support
ReadWriteMulti
.
p
everything is good ty
👍 1