# Bug in the docker container image ignition:8.\* preventing new volume mounts seeding properly **URL:** \ **Category:** Ignition\ **Tags:** ignition83, docker\ **Created:** [October 8, 2025, 3:11am UTC](https://forum.inductiveautomation.com/t/bug-in-the-docker-container-image-ignition-8-preventing-new-volume-mounts-seeding-properly/111259 "2025-10-08T03:11:59Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![Eric\_Knorr](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/eric_knorr/32/53150_2.png) [@Eric\_Knorr](https://forum.inductiveautomation.com/u/Eric_Knorr)\ **Post date:** [October 8, 2025, 7:23pm UTC](https://forum.inductiveautomation.com/t/bug-in-the-docker-container-image-ignition-8-preventing-new-volume-mounts-seeding-properly/111259/2 "2025-10-08T19:23:02Z")
Hey @sean.liew, good analysis of the issue! While I don't have all the past context for why this is the way it is, it seems to be the same root cause as the Docker bind-mount scenario [discussed here](https://forum.inductiveautomation.com/t/unable-to-mount-ignition-data-folder-in-an-external-volume-using-docker/64928) - the volume mount masks the clean template files. The official [Ignition Helm Chart](https://charts.ia.io/) handles this exact scenario in Kubernetes using an init container to seed the persistent volume before the main container starts. This is the Kubernetes-native pattern we recommend. You can see the specific implementation [here in the StatefulSet template](https://github.com/inductiveautomation/ignition-helm-chart/blob/447c084be4373821fc0d5987f12093a583072c89/ignition/templates/statefulset.yaml#L205C11-L205C46). If you're building custom manifests and your symlink workaround is working well, that's a valid solution. Otherwise, the Helm chart handles this for you automatically. --- _[View the full topic](https://forum.inductiveautomation.com/t/bug-in-the-docker-container-image-ignition-8-preventing-new-volume-mounts-seeding-properly/111259)._