My original Docker container (for SongKong) was created for use with  Qnap (http://www.jthink.net/jaikozforum/posts/list/20064.page) , created a songkong User and Group

 

RUN addgroup -S songkong \

&& adduser -S -G songkong songkong

 

But this did not work well because then SongKong did not have permission to read/write some files

So I removed the user so SongKong defaults to running as root

However we see on unRaid this means that although it can now modify any files if it moves them they get created as user root, group root umask 000. Whereas the original files are owned by nobody, group everyone umask 755 which means they cannot be modifed/deleted outside of unRAID.

 

Can anyone suggest an approach whereby SongKong Docker has access to all files but create them as the nobody user with full permissions, will this be compatible with non UNRAID systems such as Qnap ?

Edited June 26, 20197 yr by Paul Taylor

My original Docker container (for SongKong) was created for use with  Qnap (http://www.jthink.net/jaikozforum/posts/list/20064.page) , created a songkong User and Group
 
RUN addgroup -S songkong \
&& adduser -S -G songkong songkong
 
But this did not work well because then SongKong did not have permission to read/write some files
So I removed the user so SongKong defaults to running as root
However we see on unRaid this means that although it can now modify any files if it moves them they get created as user root, group root umask 000. Whereas the original files are owned by nobody, group everyone umask 755 which means they cannot be modifed/deleted outside of unRAID.
 
Can anyone suggest an approach whereby SongKong Docker has access to all files but create them as the nobody user with full permissions, will this be compatible with non UNRAID systems such as Qnap ?

Probably best to reach out to linux server.io (@CHBMB)

Sent from my NSA monitored device