immauss / openvas

Containers for running the Greenbone Vulnerability Manager. Run as a single container with all services or separate single applications containers via docker-compose.
GNU Affero General Public License v3.0
360 stars 102 forks source link

Container shows unhealthy #179

Closed farzadha2 closed 1 year ago

farzadha2 commented 1 year ago

Hi @immauss Wanted to first thank you for an amazing container currently im having an issue the docker container keeps showing unhealthy i try to restart the scannable docker container but it later turns off

image

this is my docker compose


version: "3"
services:
  openvas:
    ports:
      - "8080:9392"
    environment:
      - "PASSWORD=pwdpass"
      - "USERNAME=admin"
      - "RELAYHOST=172.17.0.1"
      - "SMTPPORT=27"
      - "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=false" # 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
    volumes:
      - "/openvas:/data"
    container_name: openvas
    image: immauss/openvas:latest
  scannable:
    image: immauss/scannable
    container_name: scannable
volumes:
  openvas:

Thank you

immauss commented 1 year ago

If it's just the scannable container, you can remove that from the compose. It's really just there to give you a test target for the scanner. Since it has a number of vulnerabilities, it is setup to only run for a few hours, then shutdown.

Now that I think about it, I'll remove it from the default docker-compose. I really shouldn't be there for just that reason.

Thanks, -Scott

farzadha2 commented 1 year ago

Hi @immauss Thank you so much for the reply, so i deleted the container and restart the openVAS container but keeps showing unhealthy whats even more odd i check the logs and shows correctly

image

image

immauss commented 1 year ago

Ah ... sorry ... I missed it the first time I looked at it. There was a bug in the health check that was corrected in the latest. You just need to pull the latest image and restart. The initial health check was not waiting long enough and things would timeout.

-Scott

immauss commented 1 year ago

Let me know if that takes care of it.

-Scott

farzadha2 commented 1 year ago

Thank you so much that did the trick