search

Secure-Compliance-Solutions-LLC / GVM-Docker

Greenbone Vulnerability Management Docker Image with OpenVAS
https://securecompliance.gitbook.io/projects/
MIT License
246 stars 91 forks source link

[Enhancement] Remove postgres from GVM. #237

Open rudnypc opened 3 years ago

rudnypc commented 3 years ago

It would be nice to have a separate postgres and GVM container.

austinsonger commented 3 years ago

@rudnypc please describe the use case and how this would benefit the community.

rudnypc commented 3 years ago

Some companies have a cluster of databases or databases as services. We also have a number of other benefits.

Dexus commented 2 years ago

I think we can make it happen, but the main problem will be that the binaries will only get the headers for the current supported postgres of the container, so if you run different postgres versions you can run into truble.

So all in all, we can make the postgres optional, but then we will not support anything that will have todo with postgres and DB at all.

Is this worth it?

schewara commented 2 years ago

Hi. To add some additional info from my perspective.

We are running a standardized PostgreSQL Container Setup which includes all the monitoring, backup, restore scripts and utilities. For example, we're using pgBackRest backing up the DB to S3 and getting this functionality into the current setup would be quite cumbersome. For us it would also be a big benefit to be able to reuse this setup, instead of reinventing the wheel for some services.

The limitations on a specific PostgreSQL Version should be less of a problem (at least in our case) as long as it is documented somewhere.