Hey guys,
I have Samba running in an unprivileged container w/ Ubuntu 16.04, and I am having problems with getting it to recognize the bind mounted ACL directory from the host. I followed this guide to setup the ACL on the host directory:
https://www.reddit.com/r/homelab/comments/4h0erv/resolving_permissions_issues_with_host_bind/
The permissions for the host directory is set as such: root:root rwx:rwx:---, ACL [g:102000:rwx]. GID 102000 pertains to the hostwrite group that all my containers will add their users to, in order to write to the directory.
The Samba user in the container (test) can recognize that the bind mounted directory has an ACL (see's the + when running ls -la), and it can successfully write to the directory. I can successfully mount that directory with the same user on a different linux machine, but it is not able to open the directory.
I'm assuming that Samba is not passing on the ACL, which is preventing the user from opening the directory. Running ls -la on the samba share does not show the + either.
This seems like it would be an issue with Samba, since I am able to read/write to the bind mounted directory in the container with the same user, but I am also not sure if the container being unprivileged is causing the problem either. When running getfacl in the container, the message "value too large for defined data type" is returned.
Any help would be greatly appreciated. I may just end up running Samba on the host end if this doesn't work out.
I have Samba running in an unprivileged container w/ Ubuntu 16.04, and I am having problems with getting it to recognize the bind mounted ACL directory from the host. I followed this guide to setup the ACL on the host directory:
https://www.reddit.com/r/homelab/comments/4h0erv/resolving_permissions_issues_with_host_bind/
The permissions for the host directory is set as such: root:root rwx:rwx:---, ACL [g:102000:rwx]. GID 102000 pertains to the hostwrite group that all my containers will add their users to, in order to write to the directory.
The Samba user in the container (test) can recognize that the bind mounted directory has an ACL (see's the + when running ls -la), and it can successfully write to the directory. I can successfully mount that directory with the same user on a different linux machine, but it is not able to open the directory.
I'm assuming that Samba is not passing on the ACL, which is preventing the user from opening the directory. Running ls -la on the samba share does not show the + either.
This seems like it would be an issue with Samba, since I am able to read/write to the bind mounted directory in the container with the same user, but I am also not sure if the container being unprivileged is causing the problem either. When running getfacl in the container, the message "value too large for defined data type" is returned.
Any help would be greatly appreciated. I may just end up running Samba on the host end if this doesn't work out.