I’m following this README: https://docs.gitlab.com/omnibus/docker/README.html to the letter except that my /srv/gitlab folder isn’t a local filesystem but a mounted NFS share which resides on a Synology NAS.
The NAS doesn’t have many options for NFS, I opted to have UNIX ACLs as default (instead of WIN) and gave the IP which runs my docker container full access.
So starting a new gitlab CE container results in this error message in its logs and the container keeps looping and never properly starts.
getfacl /srv/gitlab/
getfacl: Removing leading '/' from absolute path names
# file: srv/gitlab/
# owner: root
# group: docker
user::rwx
group::rwx
other::rwx
setfacl -mR default:group:docker:rwx /srv/gitlab/
setfacl: Option -m: Invalid argument near character 1
I’ve been reading up on setfacl for a couple of hours now but am getting nowhere. can someone help? This is definitely a ACL issue as the container starts just fine when NOT using an NFS share.
File locking: GitLab requires advisory file locking, which is only supported natively in NFS version 4. NFSv3 also supports locking as long as Linux Kernel 2.6.5+ is used. We recommend using version 4 and do not specifically test NFSv3.
I am not using NFS v4 on my Synology NAS but it can be enabled. I will try this and report back whether it fixes the issue.
That same doc also has more advice regarding no_root_squash and sync, both option sare already in use on my setup.
and that immediately triggers permission problems the likes of:
e[31mError executing action create on resource 'directory[/etc/gitlab]'e[0m
================================================================================e[0m
@jdmarble sorry to hear but on the other hand I’m glad I’m not the only one with this issue. Please let me know if you figure out any kind of solution to this.
guys and gals (@ovizii, @jdmarble), the same issues still exists even 1.5 years later.
NFS gives permission problems
Have you found any solutions to this?
If not, what does your alternative solution looks like?
Kind regards