November 5, 20241 yr if i change my appdata from /mnt/user/appdata/xxxx to /mnt/cache_nvme/appdata/xxxxx do i have to go manually through each container and change the path? Because i getting this on the appdata backup and restore, [04.11.2024 17:39:36][⚠️][ xxxxx does not have any volume to back up! Skipping. Please consider ignoring this container.
November 5, 20241 yr Community Expert you have to add the additional paths to the app data plugin. You can master set the appdata locaion installed under settings docker: If you make containers before moving yes each container will need paths edited.. also you share settings and mover may be doing something as you are no longer using the fuse symlink to access the files but a direct hardisk path to the same data... example of aditrional folder for appdata plugin to work for my needs: /mnt/cache/appdata /mnt/user/appdata /mnt/user/Dockers /mnt/vm-zfs/Dockers /mnt/vm-zfs/Dockers/ClamAV /mnt/vm-zfs/Dockers/FastAPI-DLS /mnt/vm-zfs/Dockers/Grafana /mnt/vm-zfs/Dockers/LocalAI /mnt/vm-zfs/Dockers/MakeMKV /mnt/vm-zfs/Dockers/MariaDB-Mysql /mnt/vm-zfs/Dockers/netprobe_lite /mnt/vm-zfs/Dockers/PBS /mnt/vm-zfs/Dockers/PhotoPrism /mnt/vm-zfs/Dockers/Plex /mnt/vm-zfs/Dockers/SFTP better asked on support forum:
November 5, 20241 yr Yes, you need to. You have to stop them, move every data folder, edit the container config and run them again. Except you want this for new containers only. However, the warning you get, is telling me that you are just done doing so? Because it seems to use the new path but you did not entered it as „allowed appdata sources“. or maybe you did changed the setting but the containers. Would lead to the same message. Whats your migration state? Edited November 5, 20241 yr by KluthR
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.