# How to track changes in git in the "core" resource file in the 8.3 Docker Image **URL:** \ **Category:** Ignition 8.3 Early Access\ **Created:** [September 18, 2025, 4:54am UTC](https://forum.inductiveautomation.com/t/how-to-track-changes-in-git-in-the-core-resource-file-in-the-8-3-docker-image/110742 "2025-09-18T04:54:42Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![inara.phayer](https://avatars.discourse-cdn.com/v4/letter/i/6a8cbe/32.png) [@inara.phayer](https://forum.inductiveautomation.com/u/inara.phayer)\ **Post date:** [September 18, 2025, 4:54am UTC](https://forum.inductiveautomation.com/t/how-to-track-changes-in-git-in-the-core-resource-file-in-the-8-3-docker-image/110742/1 "2025-09-18T04:54:42Z")
Looking to track changes in git of the UDT jsons inside the “core/ignition/tag-type-definitions” file in an 8.3 Docker Image. Currently the restored backup that starts with the container writes over any bind-mounts set up that file. ---
**Author:** ![ggross](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ggross/32/12668_2.png) [@ggross](https://forum.inductiveautomation.com/u/ggross)\ **Post date:** [September 19, 2025, 3:03pm UTC](https://forum.inductiveautomation.com/t/how-to-track-changes-in-git-in-the-core-resource-file-in-the-8-3-docker-image/110742/2 "2025-09-19T15:03:55Z")
When restoring a backup within Ignition, the process currently removes everything in `data/config` and then re-creates the folder structure from whatever is in the backup. This is currently the only way we can ensure completeness of the backup restoration. We are writing out the Tag and UDT JSON file definitions to disk in a predictable manner in 8.3, so the definitions should be identical even if the timestamps are not after a restore. Ultimately you should be getting the same definition after each restore. Is this not the case? Garth