Open 0x4161726f6e opened 4 years ago
This appears to be a Samba+FreeBSD issue:
https://forums.freebsd.org/threads/samba-4-4-nfsv4-acls-ad-provision-fail.56749/
What happens if you add --use-ntvfs
to the provisioning command? (as per https://www.golinuxhub.com/2014/05/your-filesystem-or-build-does-not.html?m=1)
(These were the first two Google results for your error)
I changed line 53 of init .sh to read
samba-tool domain provision --use-rfc2307 --domain=${URDOMAIN} --realm=${UDOMAIN} --server-role=dc --dns-backend=SAMBA_INTERNAL --adminpass=${DOMAINPASS} ${HOSTIP_OPTION} --use-interactive --use-ntvfs
I get this error
ERROR(<class 'samba.provision.ProvisioningError'>): Provision failed - ProvisioningError: Your filesystem or build does not support posix ACLs, which s3fs requires. Try the mounting the filesystem with the 'acl' option
Ubuntu 18.04 Docker version 19.03.6, build 369ce74a3c
Did I do something wrong?
Also getting this same issue, I tried the --use-ntvfs option to no avail
i think there is not much we can do about it, as long we're not building samba in a previous build stage. Since Samba 4.5 vxfs is not compiled by default. (--enable-vxfs) maybe i am wrong and one could use the new --with-ntvfs-fileserver parameter at provisioning.
Could anyone give this a shot with the latest build (using Samba 4.7)?
Running on FreeNAS via Ubuntu VM
Storage is mounted from FreeNAS to Ubuntu via NFSv4 9 other containers are running smoothly