Closed armaros closed 3 years ago
I'm not a Docker expert, but it seems that the problem is the fact that you create a system user and for some reason the home dir of that user is /var/empty
, which is probably wrong. Can you try adding --home /home/locast
to your adduser
command?
That might be it, or the user may have to be created inside the container in Dockerfile
.
Alternatively, add the locast user to the docker group in /etc/group
and run docker-compose as that user.
You'd have to get into a shell in the container to really see what's happening.
@armaros Any update on this?
Closing this issue, because there has been no response
The container fails to start when you attempt to run it with a service account due to a permission value on this line https://github.com/wouterdebie/locast2tuner/blob/47cc62e1a4881143c37d7737aca338fcc76ebeb1/src/config.rs#L157
Steps to reproduce the behavior:
sudo adduser --system locast
/home/locast
and set ownership to the system accountchown -R locast:nogroup /home/locast
id locast
user: <uid>:<gid>
for the system accountLogs
Configuration
Environment Debian 11
Additional context You can work around the issue by manually mounting the service account home directory and setting the Home environment variable.