setfacl: /etc/resolv.conf: Operation not supported

[queglay]

When using container station on a QNAP NAS to launch gitlab, this error is produced while spinning up the postgresql container -

Initializing certdir...                                                                                                             
Initializing logdir...                                                                                                              
Initializing rundir...                                                                                                              
Setting resolv.conf ACLs...                                                                                                         
setfacl: /etc/resolv.conf: Operation not supported                                                                                  
pg_ctl: server did not start in time        

[CheariX]

I have the same issue and don't know how to fix it

postgresql_1  | Initializing datadir...
postgresql_1  | Initializing certdir...
postgresql_1  | Initializing logdir...
postgresql_1  | Initializing rundir...
postgresql_1  | Setting resolv.conf ACLs...
postgresql_1  | setfacl: /etc/resolv.conf: Operation not supported
postgresql_1  | sudo: error in /etc/sudo.conf, line 0 while loading plugin "sudoers_policy"
postgresql_1  | sudo: /usr/lib/sudo/sudoers.so must be only be writable by owner
postgresql_1  | sudo: fatal error, unable to load plugins
postgresql_1  | ‣ Setting postgresql.conf parameter: data_directory = '/var/lib/postgresql/10/main'
postgresql_1  | sudo: error in /etc/sudo.conf, line 0 while loading plugin "sudoers_policy"
postgresql_1  | sudo: /usr/lib/sudo/sudoers.so must be only be writable by owner
postgresql_1  | sudo: fatal error, unable to load plugins

I'm basically using the latest sameersbn/docker-compose.yml on QNap QTS 4.4.2.

[smagicld]

Same problem on synology DSM:

Initializing datadir...
Initializing certdir...
Initializing logdir...
Initializing rundir...
Setting resolv.conf ACLs...
setfacl: /etc/resolv.conf: Operation not supported
pg_ctl: server did not start in time

[CheariX]

Did anyone found a solution for this?

[sunguangjiang]

2021-01-03 00:41:41	stdout	Initializing rundir...
2021-01-03 00:41:41	stdout	Initializing logdir...
2021-01-03 00:41:41	stdout	Initializing certdir...
2021-01-03 00:41:41	stdout	Initializing datadir...
2021-01-03 00:40:39	stderr	initdb: removing data directory "/var/lib/postgresql/11/main"
2021-01-03 00:40:39	stderr	child process exited with exit code 1
2021-01-03 00:40:39	stderr	2021-01-03 00:40:39.967 UTC [81] DETAIL:  Permissions should be u=rwx (0700) or u=rwx,g=rx (0750).
2021-01-03 00:40:39	stderr	2021-01-03 00:40:39.967 UTC [81] FATAL:  data directory "/var/lib/postgresql/11/main" has invalid permissions
2021-01-03 00:40:39	stdout	Initializing database...
2021-01-03 00:40:39	stderr	setfacl: /etc/resolv.conf: Operation not supported
2021-01-03 00:40:39	stdout	Setting resolv.conf ACLs...

Synology DSM6.2 image: sameersbn/postgresql:11-20200524 and sameersbn/postgresql:12-20200524

[lynic]

Same here on dsm

[saleemepoch]

Hi all,

Any solution to this? I just ran into myself for no apparent reason. Our codebase is down as a result :(

[jstdoit]

any solution now?

[ppovolotsky]

This is a problem in postgres and current functions for container, because pg change replication mechanic somewhere after 10 version, it doesnt use recovery.conf anymore, it changed to standby.signal file and primary_conninfo line in postgresql.conf
It must be fixed in functions