# Problems with running container on a Kubernetes Persistent Volume **URL:** \ **Category:** Ignition\ **Created:** [June 3, 2022, 1:11pm UTC](https://forum.inductiveautomation.com/t/problems-with-running-container-on-a-kubernetes-persistent-volume/60344 "2022-06-03T13:11:14Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![lrose](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lrose/32/62724_2.png) [@lrose](https://forum.inductiveautomation.com/u/lrose)\ **Post date:** [June 3, 2022, 1:37pm UTC](https://forum.inductiveautomation.com/t/problems-with-running-container-on-a-kubernetes-persistent-volume/60344/2 "2022-06-03T13:37:05Z")
Have you looked through this thread? > [@Kubernetes PersistentVolume - Backup /data](https://forum.inductiveautomation.com/t/kubernetes-persistentvolume-backup-data/41306/11): > > Just augmenting this thread for those that find it (since I had a couple questions on this topic, recently)… In K8s, you can leverage [initContainers](https://kubernetes.io/docs/concepts/workloads/pods/init-containers/) to seed the data volume prior to initial launch of the Gateway container [in the pod]. Here is an example deployment that leverages an init container to seed the data volume with files from the image: # Ignition K8s Example Deployment --- # Deployment apiVersion: apps/v1 kind: Deployment metadata: name: ignition-deployment spec: selector: … --- _[View the full topic](https://forum.inductiveautomation.com/t/problems-with-running-container-on-a-kubernetes-persistent-volume/60344)._