-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problems with cifs volume #170
Comments
Hey @RichardSchulz52, looks like the uid 33 is not allowed to write the volume. Since your cifs volumes work with other images, can you check as which uid the images are running and with which uid they access/write the volume? Can you please share your |
That was my first thought too, but i do not understand the user rights in a cifs context well enough. This is the used compose file:
My other containers do not have a special uid config so its 0:0 by default |
The process trying to write the repository is running as uid=33. First try: Set the ...
volumes:
otterwiki:
driver_opts:
type: cifs
o: "username=XXX,password=XXX,file_mode=0777,dir_mode=0777"
device: "\\\\XXXX\\docker_persist\\otterwiki\\otterwiki" |
The same error occurs if I add file mode and dir mode. I don't know if the error is on the server side of the cifs. To mount the remote dir UI use login credentials of a privileged user. This works for every setup so far. It also works with Windows, Mac and Android. Thats why I belive the error to be on the mount dir. |
Sounds like an error in the mount. 🤔 Can you check if there was any file or directory created by a previous try? Maybe change the path to: device: "\\\\XXXX\\docker_persist\\otterwiki\\otterwiki2" |
I used the proposed compose file and just changed the volume to a cifs mounted folder.
The container start up and a repository folder and settings.cfg file are created in the volume.
Everything works fine when I use the default volume. I can rule out trouble with the cifs setup because i use it for every volume.
Log file:
The text was updated successfully, but these errors were encountered: