Closed falkowich closed 5 years ago
Fixed.
Before all:
Please accept my apology. There're some misunderstand here. So sorry for that.
entrypoint.sh
can handle the signal. In the issue which was closed and opened by me, I mistakenly take the error recovery responsibility to the script. However, after some tests, I found it could be handled in pgsql itself properly. Just will cost a little time(some seconds). You could still optimize it.Next?
PR is on the way...
You start a container with an empty data persistent volume.
All worked fine.
It won't start due to "not-existing, not-initialized, not-correct-owner, not-correct-file-system-permission" data folder.
pg_ctl initdb
need a specific folder structure.In DockerFile
:
arachni
curl
and wget
/etc/postgres
and change the owner to postgres
/var/run/postgresql/10-main.pg_stat_tmp
and change the owner to postgres
In entrypoint.sh
of pgsql
:
gvmd
and after start openvassd
openvassd
, sleep enough time to let it flush the data cachegvmd
and gsad
now and enjoy it.Still building the image in Docker Hub CI, will test later and give a response.
by the way, have you ever meet this condition?
Thanks for the help!
Did you pull "master" from the repo?
I think that: All the dependencies should exist, and psql should work out of the box? The "only" thing that I didn't fix is decouple psql from init.d :)
About the greenbone/gsa#1364 condition. I cant recall that it happened to me before.
-- Regards Falk
Thank you so much
Closed for lack of input.
The pgsql doesn't initialized correctly and you never write error recovery handler for pgsql after docker container restart. Also docker is no-daemon design. Please stop using init.d/systemd even it is working....