first, thanks for the samba image. My issue was actually an issue with the permissions on the data volume, but I thought I'd leave the info on how to resolve it here so people may find it through the issue search:
When I followed the instructions on how to use it, I could only mount my drive in read-only mode. When I logged into the running container, I noticed that in /etc/samba/smb.conf the read only value was set to empty (wonder why, cause your script sets no as default). So I passed in -e READONLY=no when running the container. This set the value correctly, however, the image was still read-only.
Turns out, somehow the data-container was mounted with the wrong permissions. I had to do chmod -R 777 /data on the mounted data volume. I am not sure what the permissions were before or how they should be correctly, but after doing this I could write to the exposed data container.
Hope this helps if someone stumbles across the same issue. Feel free to close the issue right away :)
Hi,
first, thanks for the samba image. My issue was actually an issue with the permissions on the data volume, but I thought I'd leave the info on how to resolve it here so people may find it through the issue search:
When I followed the instructions on how to use it, I could only mount my drive in read-only mode. When I logged into the running container, I noticed that in
/etc/samba/smb.conftheread onlyvalue was set to empty (wonder why, cause your script sets no as default). So I passed in-e READONLY=nowhen running the container. This set the value correctly, however, the image was still read-only.Turns out, somehow the data-container was mounted with the wrong permissions. I had to do
chmod -R 777 /dataon the mounted data volume. I am not sure what the permissions were before or how they should be correctly, but after doing this I could write to the exposed data container.Hope this helps if someone stumbles across the same issue. Feel free to close the issue right away :)