[{"data":1,"prerenderedAt":25},["ShallowReactive",2],{"blog-tag-en-local-path-provisioner":3},[4,15],{"path":5,"title":6,"description":7,"date":8,"tags":9},"\u002Fblog\u002Fen\u002Fdocker-compose-k3s-local-path-provisioner-permission-denied","The Volume That Worked Fine in Docker Compose Threw Permission Denied the Moment It Hit K3s","Migrating from Docker Compose to K3s? A volume that worked fine locally suddenly throws Permission denied. The cause is local-path-provisioner's design. Here's how to work around it.","2026-11-05",[10,11,12,13,14],"k3s","kubernetes","docker-compose","local-path-provisioner","persistent-storage",{"path":16,"title":17,"description":18,"date":19,"tags":20},"\u002Fblog\u002Fen\u002Fk3s-local-path-provisioner-capacity-node-affinity-pvc-pending","Your K3s Pod Won't Leave Pending. The 'Ignored Capacity' and Node Affinity Trap in Local Storage","A K3s PVC stuck in Pending often traces back to one fact: local-path-provisioner never enforces capacity limits. This post digs into hypervisor thin provisioning, Volume Node Affinity Conflicts, and the backup misconceptions hiding in K3s local storage design.","2026-09-12",[10,11,21,13,22,23,24],"storage","persistent-volume","node-affinity","zfs",1794902579259]