How to avoid override the container directory when using pvc in kubernetes? How to avoid override the container directory when using pvc in kubernetes? kubernetes kubernetes

How to avoid override the container directory when using pvc in kubernetes?


This is by design. Kubelet is responsible for preparing the mounts for your container, and they can come from plaethora of different storagebackends. At the time of mounting they are empty and kubelet has no reason to put any content in them.

That said, there are ways to achieve what you seem to expect by using init container. In your pod you define init container using your docker image, mount your volume in it in some path (ie. /target) but instead of running regular content of your container, run something like

cp -r /my/dir/* /target/ 

which will initiate your directory with expected content and exit allowing further startup of the pod