I faced with starting issue of GVM a few days ago and it's still actual for the latest stable image from docker hub.
PG doesn't start in pg-gvm service because postgresql extension can't be found:
Logs of the pg-gvm service
cat /var/log/postgresql/postgresql-13-main.log
2022-07-16 12:07:54.984 UTC [23] LOG: starting PostgreSQL 13.7 (Debian 13.7-0+deb11u1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2022-07-16 12:07:55.000 UTC [23] LOG: listening on IPv4 address "127.0.0.1", port 5432
2022-07-16 12:07:55.000 UTC [23] LOG: could not bind IPv6 address "::1": Cannot assign requested address
2022-07-16 12:07:55.000 UTC [23] HINT: Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
2022-07-16 12:07:55.005 UTC [23] LOG: listening on Unix socket "/tmp/.s.PGSQL.5432"
2022-07-16 12:07:55.054 UTC [24] LOG: database system was shut down at 2022-07-15 11:38:33 UTC
2022-07-16 12:07:55.060 UTC [23] LOG: database system is ready to accept connections
2022-07-16 12:08:25.816 UTC [79] postgres@gvmd ERROR: could not open extension control file "/usr/share/postgresql/13/extension/pg-gvm.control": No such file or directory
2022-07-16 12:08:25.816 UTC [79] postgres@gvmd STATEMENT: create extension "pg-gvm";
2022-07-16 12:08:25.867 UTC [23] LOG: received fast shutdown request
2022-07-16 12:08:25.870 UTC [23] LOG: aborting any active transactions
2022-07-16 12:08:25.871 UTC [23] LOG: background worker "logical replication launcher" (PID 30) exited with exit code 1
2022-07-16 12:08:25.871 UTC [25] LOG: shutting down
2022-07-16 12:08:25.898 UTC [23] LOG: database system is shut down
736f7eef24d0
I guess that this issue the reason why gvmd container is going to infinity loop:
Logs of the gvmd service
docker-compose -p greenbone-community-edition logs -f gvmd
greenbone-community-edition-gvmd-1 | waiting 1 second for ready postgres container
greenbone-community-edition-gvmd-1 | waiting 1 second for ready postgres container
greenbone-community-edition-gvmd-1 | waiting 1 second for ready postgres container
greenbone-community-edition-gvmd-1 | waiting 1 second for ready postgres container
greenbone-community-edition-gvmd-1 | waiting 1 second for ready postgres container
A previous image worked properly and contained missed pg extension.
Can you look into it, maybe something wrong with a builder?
I faced with starting issue of GVM a few days ago and it's still actual for the latest stable image from docker hub. PG doesn't start in pg-gvm service because postgresql extension can't be found:
Logs of the
pg-gvm
servicecat /var/log/postgresql/postgresql-13-main.log
I guess that this issue the reason why gvmd container is going to infinity loop:
Logs of the
gvmd
servicedocker-compose -p greenbone-community-edition logs -f gvmd
A previous image worked properly and contained missed pg extension.
Can you look into it, maybe something wrong with a builder?