Pulling from Docker doesn't pull all Layers

Using Docker to test the software out, and a “sudo docker compose up” continuously results in “Unexpected EOF” at varying points.

Anyone know what is up with this? Why would I expect my money on a product at 2450 EURO if I can’t reasonably test the software…



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.

IMO, the best way to test the Greenbone Enterprise Edition for free, is to send a message to the Greenbone sales department and get a 7 day trial for the Enterprise Basic VM. That way, you will be operating on the same architecture as the full Greenbone Enterprise Virtual Appliances :slight_smile:

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”?

Thanks for weighing in with your thoughts Dustin. :slight_smile:

The Greenbone Community Edition is also available in other formats such as the source code installation and via Kali Linux native packages. You can easily spin up a Kali Linux VM to leverage virtualization if you don’t have an available system. My preferred method is to offload Greenbone Community Edition to a Kali Linux VPS on Linode.

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.

2 Likes

Hi @DustinB, thanks for reporting it. It should be working now and if not please let us know, thanks!

4 Likes

Thanks, the process is working. Will update if I hit any other roadblocks.

1 Like