In the main readme it states You can use prebuilt images generated by our CI workflow.
Thats not actually true is it? It looks to me like the images still have to be built locally.
Publishing your images to Docker Hub would make it much easier for people to use them.
If the crAPI docker image was available on docker hub then we would be able to add crAPI much more easily.
Without that our plan would be to build and publish the crAPI docker image to docker hub ourselves 😉
@psiinon our images are published on dockerhub through our CI. Using the docker compose file, we can use these images to start the application. The published images can be found in this link (docker-hub)
In the main readme it states
You can use prebuilt images generated by our CI workflow.
Thats not actually true is it? It looks to me like the images still have to be built locally. Publishing your images to Docker Hub would make it much easier for people to use them.We test ZAP against a set of vulnerable apps every day and publish the results: https://www.zaproxy.org/docs/scans/
If the crAPI docker image was available on docker hub then we would be able to add crAPI much more easily. Without that our plan would be to build and publish the crAPI docker image to docker hub ourselves 😉