Using Unraid 6.7.2.

I installed the Duplicacy container using the Unraid template.

Appdata is mapped to "appdata/Duplicacy", after starting the container I noticed another folder named "appdata/duplicacy", using a different owner.

 

root@Server-1:/mnt/user/appdata# ls -la
total 16
drwxrwxrwx 1 nobody users  36 Jan  6 07:47 .
drwxrwxrwx 1 nobody users  42 Jan  6 07:35 ..
drwxrwxrwx 1 nobody users 116 Jan  6 07:54 Duplicacy
drwxrwxrwx 1 root   root   18 Jan  6 07:47 duplicacy

root@Server-1:/mnt/user/appdata/duplicacy# ls -la
total 0
drwxrwxrwx 1 root   root  18 Jan  6 07:47 .
drwxrwxrwx 1 nobody users 36 Jan  6 07:47 ..
drwxrwxrwx 1 nobody users 18 Jan  6 07:47 cache
drwxrwxrwx 1 nobody users 88 Jan  6 07:59 logs

root@Server-1:/mnt/user/appdata/Duplicacy# ls -la
total 16
drwxrwxrwx 1 nobody users  116 Jan  6 07:54 .
drwxrwxrwx 1 nobody users   36 Jan  6 07:47 ..
drwx------ 1 nobody users   50 Jan  6 07:47 bin
-rw------- 1 nobody users 1117 Jan  6 07:54 duplicacy.json
-rw------- 1 nobody users  950 Jan  6 07:47 licenses.json
-rw-r--r-- 1 root   root    33 Jan  6 07:47 machine-id
-rw-r--r-- 1 nobody users  144 Jan  6 07:47 settings.json
drwx------ 1 nobody users   34 Jan  6 07:47 stats

 

It appears that the container created new content, and that Docker or Unraid mapped it using a different paths, bifurcating the storage location.

When my backup completes I will modify the container config to use all lowercase, and I will merge the files.

 

It is very strange that a container can create content outside of a mapped volume by using a different case version of the same mapped volume path.

Is this an issue with Unraid or a Docker or user error?

Ok, seems to user error, me not noticing it and the template creator

In the container config the cache and logs folders are mapped to "appdata/duplicacy/...", while the config folder is mapped to "appdata/Duplicacy".

Will fix template mappings.

Definitely a user error, and one that can crop up in other ways. Linux is case-sensitive, as simple as that. If you use different case you are specifying a different path. Better check all your docker mappings.

 

Better check the settings within each of your docker applications also. A mistake there is the most common cause of filling docker image. If the application specifies a path that uses different case than the mapping, then that path is not mapped and so is inside the docker image.

I'll put in a PR with them to change that template, as by default the appdata for /config will always wind up being with a capital D

Thanks, where is the template code hosted, I asked saspus, the author of the container, and he knew nothing of the Unraid template?

38 minutes ago, ptr727 said:

Thanks, where is the template code hosted, I asked saspus, the author of the container, and he knew nothing of the Unraid template?

https://github.com/selfhosters/unRAID-CA-templates