Closed bwittmeyer closed 1 year ago
Is this solved?
Not really, No updates were made documentation. There was a reference to a new greenbone-feed-sync container however no details on how to use it,
On Fri, Sep 29, 2023 at 12:08 Jason Culligan @.***> wrote:
Is this solved?
— Reply to this email directly, view it on GitHub https://github.com/greenbone/docs/issues/367#issuecomment-1741233352, or unsubscribe https://github.com/notifications/unsubscribe-auth/AUWKQEYKUCT72HMHJBBEC73X436CVANCNFSM6AAAAAA35B6T4Y . You are receiving this because you authored the thread.Message ID: @.***>
No this isn't solved. My commit should just have referenced this issue but not closed it.
Expected behavior
docker-compose -f $DOWNLOAD_DIR/docker-compose.yml -p greenbone-community-edition \ run --rm ospd-openvas greenbone-nvt-sync
manual update of greenbone feeds
Actual behavior
manual update will fail since greenbone-nvt-sync and greenbone-feed-sync are nolonger part of the ospd-openvas and gvmd containers.
Fix update documentation to remove this reference. Alternatively update the documentation to explain what would be required to use the new greenbone-feed-sync python script running on the host.