It's about the user inside your container. As you map volumes the user inside the container will own the folder you map. And you probably created on the host first with your own user or root. As such it can map but can't write to it. What I in general do is to have a user setup on my docker host. Like dockeruser:dockeruser Uid 1001 gid 1001 Then I pass the same Uid and gid to my containers as env. And set the folder to 1001:1001
Now if you don't care about security just do a chmod 777 on your folder.
exec in your container check the uid anf gid of your "moonlightbot" user
make a user dockeruser edit the /etc/passwd and groups file and modify the uid and gid to match the ones in your container
it is necessary to execute a
sudo chmod 777 -R fuseki-dev/ fuseki-live/
before writing to the corresponding folders.comment 1 from FK
suggested solutions: https://www.reddit.com/r/docker/comments/hjsipd/permission_denied_with_volumes/
or more info also e.g. here: https://mydeveloperplanet.com/2022/10/19/docker-files-and-volumes-permission-denied/
comment 2 from FK
quickfix could also be something like:
sudo chown -R 1000:root fuseki-dev/ fuseki-live/