[BUG] Unable to start container using compose file

Describe the bug
First start with NEWDB=true and SKIPSYNC=false, it managed to download bases, then after a while, it starts to loop in a restart process. Then I stopped the container, changed NEWDB to false, SKIPSYNC to true, but pgsql seems to fail to start.

To Reproduce
Steps to reproduce the behavior:

1. Include how you started the container.

services:
  openvas:
    hostname: openvas
    container_name: openvas
    environment:
      - "PASSWORD=<REDACTED>"
      - "USERNAME=<REDACTED>"
      - "RELAYHOST=<REDACTED>"
      - "SMTPPORT=25"
      - "REDISDBS=512" # number of Redis DBs to use
      - "QUIET=false"  # dump feed sync noise to /dev/null
      - "NEWDB=false"  # only use this for creating a blank DB 
      - "SKIPSYNC=true" # Skips the feed sync on startup.
      - "RESTORE=false"  # This probably not be used from compose... see docs.
      - "DEBUG=false"  # This will cause the container to stop and not actually start gvmd
      - "HTTPS=false"  # wether to use HTTPS or not
      - "GMP=9390"    # to enable see docs
      - "PGVER=15" # Set postgresql version ... either 13 or 15
    networks:
      - openvas
    restart: unless-stopped
    volumes:
      - "<REDACTED>:/data"
    image: docker.io/immauss/openvas:26.07.27.01

2. When did the issue occur?
   From the beginning.

Expected behavior
Well, pgsql should start without throwing "Stopping postgresql"

Screenshots
N/A

Environment (please complete the following information):

• OS: Alma Linux 10
• Memory available to OS: 71GB
• Container environment used with version: Docker

logs ( commands assume the container name is 'openvas' )

docker-compose

docker.log

Additional context
N/A