Thor_Storm

It seems to me like the directory where volumes are stored is not stored in memory on my part, and in the Unraid docker image file (which maybe isn't ideal, but it works): Filesystem Size Used Avail Use% Mounted on /dev/loop2 100G 77G 22G 78% /var/lib/docker /dev/loop2: [0040]:1613693 (/mnt/cache/system/docker/docker.img) Is there something in the way that Unraid handles that mapping, or is it something with the way the app interacts with docker volumes? I was positive this was working for me before updating to Unraid 7.x, so maybe I'm missing something.

I have recently struggled a lot with backing up containers with docker volumes mapped to them. Saw something in the road map about distinguishing between bind voumes and named volumes, but unsure what that entails. My struggle is this: [11.05.2026 05:02:53][❌][teamspeak-server-1] 'teamspeak-data' does NOT exist! Please check your mappings! Skipping it for now. [11.05.2026 05:02:54][debug][teamspeak-server-1] usorted volumes: Array The volume exists: docker volume ls | grep -i 'teamspeak' local teamspeak-data It is mapped like such: volumes: - teamspeak-data:/var/tsserver It's from here I am unsure what to do. This problem happens to a lot of containers, all of which have a docker-volume. Unsure if the backup is worth anything if it truly hasn't taken the data in the volume. If anyone has any advice, it would be much appreciated.