Hi Dustin and thanks for your post. The Greenbone Community Docker Containers are not the same as the Greenbone Enterprise Edition. So, your goal to “test the software” is not reasonable. The Greenbone Community Editions are for developers and are often used to test new features. Therefore, stability is not the priority.
Even still, in that case how would any developer test the software when the docker repo being hosted by the organization seems to be stalling or completely failing at hosting the files they need to “test new features”?
Therefore, there shouldn’t be too much of a barrier to find a method of testing Greenbone Community Edition even despite some short term downtime of the container registry.
However, as I mentioned, the most accurate way to test the Greenbone Enterprise Edition is to request a Enterprise VM from the sales department.
Also, I should add that the new Greenbone Enterprise Basic version will not expire as the previous Greenbone Enterprise Trial edition did. Once the 7 day free trial version is finished, it will revert to the Greenbone Community Feed.
Therefore, once you get your hands on the Greenbone Enterprise Basic Trial VM, you can use it to test the stability and reliability of Greenbone for an extended period of time.
I think that developers and Linux system admins will be well versed in troubleshooting some install issues and generally able to get Greenbone Community Edition running despite fast moving dependency ecosystem in the wild.