Two somewhat related problems:

One, I can't explain why, but I've lost count of the number of people that use mounted hosted directories (bind mounts) while configuring Additional volumes for apparently additional granularity... only to have everything end up in the same spot (pointless complexity). So this:

$ docker run -d \
-v nextcloud:/var/www/html \
-v apps:/var/www/html/custom_apps \
-v config:/var/www/html/config \
-v data:/var/www/html/data \
-v theme:/var/www/html/themes/<YOUR_CUSTOM_THEME> \
nextcloud

which may be useful... becomes something like this when turned into a bind mount:

$ docker run -d \
-v ./nextcloud:/var/www/html \
-v ./nextcloud/apps:/var/www/html/custom_apps \
-v ./nextcloud/config:/var/www/html/config \
-v ./nextcloud/data:/var/www/html/data \
-v ./nextcloud/theme:/var/www/html/themes/<YOUR_CUSTOM_THEME> \
nextcloud

... which is not useless, but breaks things (apps - see next item);

Two, when people attempt to "translate" the above example into a bind mounts, this one causes us support problems: -v apps:/var/www/html/custom_apps \. It seems to get often translated to something like ./nextcloud/apps:/var/www/html/custom_apps. That is a clearly broken setup.

Ideas to solve:

• Rename the named volume apps in the example to custom_apps for added clarity
• Add an example that uses bind mounts to avoid the apparent "translation errors" that occur (and also giving us another opportunity to point out it's a pointless complication unless the source of the mount is going to be somewhere else relative all the other subfolders)