Closed leolobato closed 2 years ago
Hi there!
In the container Liquidsoap runs under a non-root user, so I'm guessing it has something to do with file permissions.
What permissions does your /mnt/music/Radio
directory have?
Does issuing this command chmod -R 774 /mnt/music/Radio
help?
I was able to solve it by changing the UID of the radio
user created by the Dockerfile, to match the UID of my host system.
Before my fix, it would show (inside the container):
radio@2d39eeb652eb:/$ ls -la /
total 60
...
drwxrwx--- 2 1000 1000 0 Apr 17 07:43 music
...
So I modified the Dockerfile to use this UID/GID:
RUN groupadd -g 1000 radio && \
useradd -m -r -u 1000 -s /bin/bash -g radio radio && \
And then recreated the docker image from this local copy and it worked:
radio@2d39eeb652eb:/$ ls -la /
total 60
...
drwxrwx--- 2 radio radio 0 Apr 17 07:43 music
...
There should be some better, automated way to do this but I'm not super familiar with Docker.
Looks like your /mnt/music/Radio
directory doesn't have read permission set for all users.
So the command chmod -R 774 /mnt/music/Radio
issued from the host system (not from the inside of the container) would also help to resolve this.
Thank you for taking the time to setup this docker container.
I've tried replacing my standalone liquidsoap setup by this container (use Portainer) but am running into the following issue, only for the
/music
volume:This is my docker compose file:
If I use the console into the container and try to access the
/music
mounted volume, I do get access denied.