Replies: 1 comment
-
lol solved my own problem. Using user: UID:GID outside the environment section fixes the permissions mismatch. For some reason doing so in the environment section wasn't doing so. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I don't know if this is intended behavior or not, but to get docker container flood:master to work I was required to set the host "config" folder permissions at 777.
I have the container puid:pgid set at 1000:1000 which matches the setting for the host folder. However, the only permissions that would not result in "can not access runtime directory" were 777. 755 and 775 blocked the container from reading.
it would be nice to not have this directory wide open to the system.
Side Note: the master branch appears to be woking with qbittorrent 4.4.5
Beta Was this translation helpful? Give feedback.
All reactions