Verdaccio cannot find config.yaml file when launching via docker with bind mounting

[bradws]

PROBLEM

I'm wanting to use Verdaccio in a Docker container with bind mounting to persist my data, but I'm getting an error when launching it. The error in the terminal is:

"cannot open config file /verdaccio/conf/config.yaml: false"

The command I'm using is:

sudo docker run -it --rm --name verdaccio \
  -p 4873:4873 \
  -v /volume2/Main/dev/docker-volumes/verdaccio/conf:/verdaccio/conf \
  -v /volume2/Main/dev/docker-volumes/verdaccio/storage:/verdaccio/storage \
  -v /volume2/Main/dev/docker-volumes/verdaccio/plugins:/verdaccio/plugins \
  verdaccio/verdaccio

WHAT I DID

1. Verdaccio works fine when I DON'T persist my data. For example when launching the container with the following command, Verdaccio works perfectly:
   sudo docker run -it --rm --name verdaccio -p 4873:4873 verdaccio/verdaccio ...but obviously everything is erased once the container stops.

2. The command works fine and Verdaccio retains the data if my bind mounting goes to a folder that is directly on the HOST file system. For example, if i create a folder like /test-verdaccio/conf etc and use the docker -v switch to bind mount it there, it works fine.

3. My 'volume2' is BTRFS, and has an entry in my /etc/fstab file like this:
   /dev/vg1/volume_2 /volume2 btrfs auto_reclaim_space,synoacl,ssd,relatime 0 0

4. I can use other docker containers that access this folder with no problems
   e.g. /volume2/Main/dev/docker-volumes/nginx

5. As per the website, I did:
   5.1 Copy the docker.yaml file from https://github.com/verdaccio/verdaccio/blob/5.x/conf/docker.yaml and put it into the 'conf' folder and renamed if to config.yaml
   5.2 I tried it with leaving the 'conf' folder empty
   5.3 I tried it with setting the permissions sudo chown -R 10001:65533 on all the folders and files.

6. My operating system is Linux on my NAS device which is a Synology 1819+ Device with the following details:
   Linux version 4.4.59+ (root@build2) (gcc version 4.9.3 20150311 (prerelease) (crosstool-NG 1.20.0) ) #25426 SMP PREEMPT Tue May 12 04:54:42 CST 2020
   Linux DiskStation 4.4.59+ #25426 SMP PREEMPT Tue May 12 04:54:42 CST 2020 x86_64 GNU/Linux synology_denverton_1819+

7. I don't have a 'audit.log' file, but I noticed these errors in the 3 log files below. It doesn't seem to be able to create a socket.

auth.log

2023-09-21T16:02:04+08:00 DiskStation sudo: admin : TTY=pts/15 ; PWD=/var/log ; USER=root ; COMMAND=/usr/local/bin/docker run -it --rm --name verdaccio -p 4873:4873 -v /volume2/Main/dev/docker-volumes/verdaccio/conf:/verdaccio/conf -v /volume2/Main/dev/docker-volumes/verdaccio/storage:/verdaccio/storage -v /volume2/Main/dev/docker-volumes/verdaccio/plugins:/verdaccio/plugins verdaccio/verdaccio
2023-09-21T16:02:04+08:00 DiskStation sudo: pam_unix(sudo:session): session opened for user root by admin(uid=0)
2023-09-21T16:02:12+08:00 DiskStation sudo: pam_unix(sudo:session): session closed for user root

kern.log

2023-09-21T16:02:15+08:00 DiskStation kernel: [1034317.161005] BTRFS error (device md2): cannot find qgroup item, qgroupid=1413 !
2023-09-21T16:02:15+08:00 DiskStation kernel: [1034317.161005]
2023-09-21T16:02:15+08:00 DiskStation kernel: [1034317.219706] BTRFS error (device md2): cannot find qgroup item, qgroupid=1412 !
2023-09-21T16:02:15+08:00 DiskStation kernel: [1034317.219706]

messages

2023-09-21T16:02:07+08:00 DiskStation ntpd[8839]: bind(27) AF_INET6 fe80::c0fa:feff:feac:eec0%99#123 flags 0x11 failed: Cannot assign requested address
2023-09-21T16:02:07+08:00 DiskStation ntpd[8839]: unable to create socket on docker9e8ef51 (77) for fe80::c0fa:feff:feac:eec0%99#123
2023-09-21T16:02:15+08:00 DiskStation kernel: [1034317.161005] BTRFS error (device md2): cannot find qgroup item, qgroupid=1413 !
2023-09-21T16:02:15+08:00 DiskStation kernel: [1034317.161005]
2023-09-21T16:02:15+08:00 DiskStation kernel: [1034317.219706] BTRFS error (device md2): cannot find qgroup item, qgroupid=1412 !
2023-09-21T16:02:15+08:00 DiskStation kernel: [1034317.219706]

Please help! And please note again that other docker containers are able to bind mount with no problems.

I'm not a Linux guy, but I get the feeling it may have something to do with permissions? I log into linux as 'administrator' but when prefixing with 'sudo' I go into a 'root' mode.