I seem to be having an issue with this vs. the original appdata backup: 'file has changed' as experience by several other people in the thread:
[13.01.2024 09:25:55][❌][FoundryVTT10] tar creation failed! Tar said:
tar: /mnt/user/AppData/FoundryVTT10/data/Data/modules/JB2A_DnD5e/Library/Generic/Impact/GroundCrackFrostImpact_01_Regular_White_600x600.webm: file changed as we read it;
tar: /mnt/user/AppData/FoundryVTT10/data/Data/modules/JB2A_DnD5e/Library/Generic/Impact: file changed as we read it;
tar: /mnt/user/AppData/FoundryVTT10/data/Data/modules/JB2A_DnD5e/Library/Generic: file changed as we read it;
tar: /mnt/user/AppData/FoundryVTT10/data/Data/modules/JB2A_DnD5e/Library: file changed as we read it;
tar: /mnt/user/AppData/FoundryVTT10/data/Data/modules/JB2A_DnD5e: file changed as we read it;
tar: /mnt/user/AppData/FoundryVTT10/data/Data/modules: file changed as we read it;
tar: /mnt/user/AppData/FoundryVTT10/data/Data: file changed as we read it;
tar: /mnt/user/AppData/FoundryVTT10/data: file changed as we read it
id: 89a9402e-820c-47c8-b066-a6a8baae4ee8
While it isn't reliably that file, it is reliably that folder that has a "changed as we read it". Any recommendations for finding what is touching that file with the docker stopped? That container doesn't share mappings with anything else, and it doesn't matter if the container is mapped via FUSE or not (I haven't gotten around to setting up exclusive share yet).
Editing to add:
I changed the backup type from "stop, backup, start container" to "stop all containers, backup, start all containers" and that seems to have given whatever process enough time to let go of those files before the plugin tries to touch it.
I have noticed in the past that that particular container isn't receptive to being restarted from the gui. It need to be stopped - wait - restarted. I don't know how to explain that behavior from a docker POV but it certainly seems to track with this. Either way issue seems to be resolved for me.
When this happened to me, it was because the appdata source paths are case sensitive. By default the plugin looks for paths of
So it didn't automatically believe my paths (/mnt/user/AppData and /mnt/cache/AppData) were internal volumes. I just added my paths to appdata source(s):