Asking for update to website Unraid install.
Greetings, love all that you're doing and working towards. I'm hoping I could ask for a small update to your websites Unraid install page.
While your guide using the docker-compose files works just fine, Unraid will support volumes located in the depths of the file system /var/lib/docker/volumes getting to them could be difficult for the new user.
Unraid uses their appdata file location as it's dumping ground for docker data. This allows for appdata to easily be backed up via plug ins, and ease of finding/deleting data if you ever wanted to start over. I have yet to find an "easy" way to purging volumes, which may be over the head of a new user. I modified my docker-compose file and ENV file to allow for mapping those volumes to a centralized Immich folder located in the appdata folder.
I've yet to see any ill side effects of doing this as all references to needed volumes were changed to the new location via variables which are defined in the ENV file.
One note I will add, and I'm not sure how the config folders/files for Immich would handle the weird way Unraid does it's file system when dropped onto a share that distributed over several drives . I would recommend, at least for the appdata folders, that they be assigned to a specific drive (in my case, my nvme drive). I've had other dockers that wouldn't run if set to a share that's distributed over disks (/mnt/user/<share_name>) Just an idea, as it took me a quick minute to figure out why I couldn't start over completely. It was because those volume folders were still in /var/lib/docker/volumes .
While your guide using the docker-compose files works just fine, Unraid will support volumes located in the depths of the file system /var/lib/docker/volumes getting to them could be difficult for the new user.
Unraid uses their appdata file location as it's dumping ground for docker data. This allows for appdata to easily be backed up via plug ins, and ease of finding/deleting data if you ever wanted to start over. I have yet to find an "easy" way to purging volumes, which may be over the head of a new user. I modified my docker-compose file and ENV file to allow for mapping those volumes to a centralized Immich folder located in the appdata folder.
I've yet to see any ill side effects of doing this as all references to needed volumes were changed to the new location via variables which are defined in the ENV file.
One note I will add, and I'm not sure how the config folders/files for Immich would handle the weird way Unraid does it's file system when dropped onto a share that distributed over several drives . I would recommend, at least for the appdata folders, that they be assigned to a specific drive (in my case, my nvme drive). I've had other dockers that wouldn't run if set to a share that's distributed over disks (/mnt/user/<share_name>) Just an idea, as it took me a quick minute to figure out why I couldn't start over completely. It was because those volume folders were still in /var/lib/docker/volumes .
0 Replies