-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Upgrading from 10-9 to 1x-xx fails on DSM devices: DETAIL: Permissions should be u=rwx (0700) or u=rwx,g=rx (0750). #2224
Comments
Why not try |
I run into the following issue when I do that:
I also tried doing: |
Had the same problem. Comment out this line and build the PostgreSQL image by yourself. Worked for me! Best regards |
Met same issue |
okay.... I figure out a way to solve it, first create 11/main folder with correct owner , then create an empty file under 11/main, it will workaround |
First of all thank you all for shareing your experiences and Tips. I followed docker-compose setup of this excellent tutorial and can confirm UTC [402] FATAL: data directory "/var/lib/postgresql/12/main" has invalid permissions Error. I setup folders like this with this docker compose services: postgresql: gitlab:
–––– The fix of lynic didn't work for me... |
Anyone end up finding a fix for this? |
@vkarps I'm currently deploy gitlab on synology too and it's working. I see a difference with your volume mount, the |
I managed to get it work somehow:
|
Just make sure the main folder is created. If the folder itself is missing, you will get the invalid permission error |
I'm running gitlab on an Synology box running the latest version of DSM (6.2.3-25426 Update 2). Also I've recreated this issue on multiple different boxes of Synology and I'm not sure how to resolve this. I've tried different version of postgresql and the only reason really why I've tried updating is because gitlab requires it with version 13.xx and on.
It stays stuck in this loop:
Any help with this would be appreciated.
Thank you.
The text was updated successfully, but these errors were encountered: