Closed hugeps closed 2 weeks ago
One way around this problem is to run:
export COMMUNITY_NVT_RSYNC_FEED=rsync://feed.community.greenbone.net:/nvt-feed
export COMMUNITY_CERT_RSYNC_FEED=rsync://feed.community.greenbone.net:/cert-data
export COMMUNITY_SCAP_RSYNC_FEED=rsync://feed.community.greenbone.net:/scap-data
So, @mikesplain might update this section in README.md
:
docker exec -it openvas bash
## inside container
export FEED=feed.community.greenbone.net
export COMMUNITY_NVT_RSYNC_FEED=rsync://$FEED:/nvt-feed
export COMMUNITY_CERT_RSYNC_FEED=rsync://$FEED:/cert-data
export COMMUNITY_SCAP_RSYNC_FEED=rsync://$FEED:/scap-data
greenbone-nvt-sync
openvasmd --rebuild --progress
greenbone-certdata-sync
greenbone-scapdata-sync
openvasmd --update --verbose --progress
/etc/init.d/openvas-manager restart
/etc/init.d/openvas-scanner restart
Is @mikesplain still maintaining this?
I just run the container with this: docker stop openvas && docker rm openvas
docker pull mikesplain/openvas
docker run -d -p 3344:443 -p 9390:9390 \
-e PUBLIC_HOSTNAME=openvas.myweb.com \
-e FEED="feed.community.greenbone.net" \
-e COMMUNITY_NVT_RSYNC_FEED="rsync://$FEED:/nvt-feed" \
-e COMMUNITY_CERT_RSYNC_FEED="rsync://$FEED:/cert-data" \
-e COMMUNITY_SCAP_RSYNC_FEED="rsync://$FEED:/scap-data" \
--network nginxproxymgr_default \
--name openvas \
-h openvas \
-v /opt/openvas/mgr:/var/lib/openvas/mgr/ \
mikesplain/openvas
Thank you ramonchiara, perfectly solved this problem
You can also edit the configuration file in the container itself according to the method
https://community.greenbone.net/t/shutting-down-gcf-http-download/5339
Community feed is now located here
feed.community.greenbone.net:
IP address: 2a0e:6b40:20:106:20c:29ff:fe67:cbb5 Legacy IP address: 45.135.106.142