Greenbone service is not responding

Hello I deployed the container on a machine with the default docker compose file and then used caddy as a reverse proxy (for different reason). I can get into the login interface but keep getting the message

“The Greenbone Vulnerability Manager service is not responding. This could be due to system maintenance. Please try again later, check the system status, or contact your system administrator.”

I check the browser console and see this error message: “Login failed. GMP Service is down.”
And inside the container logs I get the following:

gvmd-1                 | CONTEXT:  SQL statement "CREATE INDEX result_vt_epss_by_vt_id ON result_vt_epss (vt_id);"
gvmd-1                 | PL/pgSQL function create_index(text,text,text,text) line 1 at EXECUTE
gvmd-1                 | SQL statement "SELECT create_index ('public', index_name, table_name, columns)"
gvmd-1                 | PL/pgSQL function create_index(text,text,text) line 1 at PERFORM
gvmd-1                 |  (7)
gvmd-1                 | md manage:WARNING:2025-07-03 13h01.21 utc:16: sql_exec_internal: SQL: SELECT create_index ('result_vt_epss_by_vt_id',                     'result_vt_epss', 'vt_id');
gvmd-1                 | md manage:WARNING:2025-07-03 13h01.21 utc:16: sqlv: sql_exec_internal failed
gvmd-1                 | md   main:MESSAGE:2025-07-03 13h01.21 utc:19:    Greenbone Vulnerability Manager version 26.0.0 (DB revision 259)
gvmd-1                 | md manage:   INFO:2025-07-03 13h01.21 utc:19:    Modifying setting.
gvmd-1                 | md manage:MESSAGE:2025-07-03 13h01.21 utc:19: No SCAP database found
gvmd-1                 | md manage:WARNING:2025-07-03 13h01.23 utc:19: sql_exec_internal: PQexec failed: ERROR:  could not extend file "base/16385/59454": No space left on device
gvmd-1                 | HINT:  Check free disk space.
gvmd-1                 | CONTEXT:  SQL statement "CREATE INDEX result_vt_epss_by_vt_id ON result_vt_epss (vt_id);"
gvmd-1                 | PL/pgSQL function create_index(text,text,text,text) line 1 at EXECUTE
gvmd-1                 | SQL statement "SELECT create_index ('public', index_name, table_name, columns)"
gvmd-1                 | PL/pgSQL function create_index(text,text,text) line 1 at PERFORM
gvmd-1                 |  (7)
gvmd-1                 | md manage:WARNING:2025-07-03 13h01.23 utc:19: sql_exec_internal: SQL: SELECT create_index ('result_vt_epss_by_vt_id',                     'result_vt_epss', 'vt_id');
gvmd-1                 | md manage:WARNING:2025-07-03 13h01.23 utc:19: sqlv: sql_exec_internal failed
gvmd-1                 | starting gvmd
gvmd-1                 | md   main:MESSAGE:2025-07-03 13h01.23 utc:20:    Greenbone Vulnerability Manager version 26.0.0 (DB revision 259)
gvmd-1                 | md manage:MESSAGE:2025-07-03 13h01.23 utc:20: No SCAP database found
gvmd-1                 | md manage:WARNING:2025-07-03 13h01.23 utc:20: sql_exec_internal: PQexec failed: server closed the connection unexpectedly
gvmd-1                 | 	This probably means the server terminated abnormally
gvmd-1                 | 	before or while processing the request.
gvmd-1                 |  (7)
gvmd-1                 | md manage:WARNING:2025-07-03 13h01.23 utc:20: sql_exec_internal: SQL: CREATE MATERIALIZED VIEW result_vt_epss AS (  SELECT oid AS vt_id,    epss_score,    epss_percentile,    epss_cve,    epss_severity,    max_epss_score,    max_epss_percentile,    max_epss_cve,    max_epss_severity  FROM nvts);
gvmd-1                 | md manage:WARNING:2025-07-03 13h01.23 utc:20: sqlv: sql_exec_internal failed
gvmd-1                 | Starting gvmd failed
gvmd-1                 | waiting 1 second for ready postgres container
gvmd-1                 | waiting 1 second for ready postgres container
gvmd-1                 | waiting 1 second for ready postgres container
.
.
.

Hello,

and welcome to this community forums.

It seems the posted log part here already indicates that the source of the problem is inadequate storage space for operating the containers: