Closed ycodryn closed 3 years ago
Good Evening I am experiencing a similar issue. Here is a screen capture of the error I am receiving:
Can you both try to manually chown the data directory from the host to be the proper user and then restart the container? I think the issue is that the permissions aren't being set properly on first run.
e.g. chown -R 1000:1000 ./data
I'm using unraid and had the same issue. Thank you @jshridha for the obvious fix :)
Thanks jshridha I will try tonight, all my containers are created with main root user uid/gid so mybe this is the problem.
This is fixed in: 651429e1688232489729beda836bf271719a0b94 Permissions on data directory are now set at startup. Builds take a while but should hit docker hub soon.
Feel free to reopen if the issue persists for you. Thanks for posting!
Using the vaapi dockerfiles, after creating the container and running it, I`m getting that message. Also using -v /volume1/docker/blueiris:/home/wineuser/prefix:rw, container is not creating files inside mapped volume edit: all my containers are created with my main user uid/gid and all are working correctly but this one refuse to create files inside mapped volume. I tried to change /home/wineuser/prefix with /root/prefix on all files inside docker before creation and now is semi populating the mapped volume.