How to Set Up Greenbone (OpenVAS) with Docker Compose

Greenbone Community Edition is the free, open-source version of the Greenbone vulnerability scanner, the project most people still know as OpenVAS. Running it with Docker Compose is the quickest way to get a working scanner on a home lab box or a small office server, without building a dozen components from source.
This guide follows Greenbone’s own container docs and their current compose.yaml. By the end you’ll have the full stack running, a proper admin password set, the feeds loaded and your first scan under way.
Scan only what you own. A vulnerability scanner sends a lot of probing traffic. Point it at your own servers and network, or at systems you have written permission to test, and nothing else.
What is Greenbone Community Edition?
Greenbone Community Edition bundles the OpenVAS scanner, the Greenbone Vulnerability Manager (gvmd) that stores targets, tasks and results, and the Greenbone Security Assistant (GSA), the web interface you click around in. It checks your hosts against a community feed of vulnerability tests (VTs), plus SCAP and CERT data, and produces reports you can sort by severity.
In the container setup each piece runs in its own container: a set of small data containers copy the feed into Docker volumes, then gvmd, ospd-openvas, openvasd, Redis and PostgreSQL do the work, and nginx serves the web interface.
Greenbone says the container setup is meant for testing and getting familiar with the product rather than production. For a home lab or a small business checking its own kit, that’s usually exactly what you want.
What’s changed in 2026
If you set Greenbone up a while ago, or you’re following an older guide, these are the changes that matter:
- The free Community Feed covers less than it used to. New vulnerability tests in the Community Feed dropped sharply from January 2026. A Greenbone staff member confirmed on the forum in July 2026 that this is intentional (though “not necessarily permanent”), to promote the Enterprise feed, and that Community coverage is now mainly Notus checks and selected Linux distributions. In practice: Greenbone CE is still very useful for Linux servers and network services, but don’t treat a clean report as proof that everything is patched, especially on Windows machines.
- The compose file changed in February 2026. A new
gvm-configcontainer now provides the nginx configuration and a self-signed certificate, nginx serves the web interface over HTTPS, andgsadruns as an API-only service behind it. Old compose files withgreenbone/*Docker Hub images or a plain HTTP port are out of date. - Fewer image tags since 13 April 2026. Greenbone’s registry (
registry.community.greenbone.net) now only offers thelatest,latest-slim,edge,edge-slim,stable,stable-slimandcommunitytags. The address didn’t change, and the official compose file works as is, but if you pinned any other tag in your own compose file, switch to one of these ordocker compose pullwill fail. - Security advisories: at the time of writing there are no published security advisories for gvmd on GitHub. The best protection is still to pull updated images regularly (see “Keep the feed and containers up to date” below).
What you need
- A Linux host. Greenbone’s docs list Debian stable, Ubuntu 24.04 LTS, Fedora and CentOS Stream 9.
- At least 2 CPU cores, 4 GB RAM and 20 GB of disk. Greenbone recommends 4 cores, 8 GB RAM and 60 GB, and the extra headroom makes feed loading and scans noticeably less painful.
- Docker Engine with the Docker Compose v2 plugin (the
docker composecommand, not the olddocker-compose). curlandca-certificates.
The docs don’t pin a Docker version; any current Docker Engine release from Docker’s own repository is fine.
Step 1: Install Docker and the Compose plugin
Follow Docker’s official Docker Engine install guide for your distribution. If you’re on Ubuntu, my Docker on Ubuntu guide walks through it.
Then install the two small tools Greenbone needs:
# Debian or Ubuntu
sudo apt install ca-certificates curl
# Fedora or CentOS Stream
sudo dnf install ca-certificates curl
Add your user to the docker group so you don’t need sudo for every command:
sudo usermod -aG docker $USER && su $USER
Success looks like: docker compose version prints a v2 version number.
Step 2: Download the official compose file
Older guides (including the first version of this one) pasted a long docker-compose.yml using greenbone/* images from Docker Hub. Greenbone has since moved its images to its own registry, registry.community.greenbone.net, and now publishes a single compose.yaml on a rolling basis. Download theirs rather than copying one from a blog, so you always get the current service list:
export DOWNLOAD_DIR=$HOME/greenbone-community-edition && mkdir -p $DOWNLOAD_DIR
curl -f -O -L https://greenbone.github.io/docs/latest/_static/compose.yaml --output-dir "$DOWNLOAD_DIR"
It’s worth a quick read before you start it. You’ll see about twenty services, including:
- Data containers (
vulnerability-tests,notus-data,scap-data,cert-bund-data,dfn-cert-data,data-objects,report-formats,gpg-data) that copy feed data into volumes. pg-gvm(PostgreSQL) andredis-server.gvmd,ospd-openvas,openvasdandopenvas, the manager and scanner.gsadandgsa, the web app, served bynginx.gvm-config, which generates a self-signed TLS certificate for nginx.
The only ports published on the host are on nginx, and they’re bound to localhost:
- 127.0.0.1:443:443
- 127.0.0.1:9392:9392
Leave that as it is for now. Step 6 covers reaching it from another machine safely.
Step 3: Pull the images and start the stack
docker compose -f $DOWNLOAD_DIR/compose.yaml pull
docker compose -f $DOWNLOAD_DIR/compose.yaml up -d
To watch everything come up:
docker compose -f $DOWNLOAD_DIR/compose.yaml logs -f
Success looks like: docker compose -f $DOWNLOAD_DIR/compose.yaml ps shows the long-running services (gvmd, ospd-openvas, nginx and friends) as running. The data containers do their copy and then sit idle; that’s expected.
Greenbone also publishes a setup-and-start-greenbone-community-edition.sh script that does steps 2 to 4 in one go and prompts for the admin password. It’s handy, but doing the steps by hand means you know what’s running.
Step 4: Set the admin password
The stack creates a user called admin with the password admin. Change it straight away:
docker compose -f $DOWNLOAD_DIR/compose.yaml \
exec -u gvmd gvmd gvmd --user=admin --new-password='<password>'
Wrap the password in single quotes if it contains special characters such as $. If the command fails because gvmd isn’t ready yet, give it a minute and run it again.
Step 5: Wait for the feed to update
This is the step people skip, and then wonder why their first scan found nothing. Feed loading happens in two stages: the data containers copy the feed into volumes, then gvmd and ospd-openvas load it. Greenbone says this can take anywhere from several minutes to hours, especially the first time. Scans started before it finishes give incomplete results.
Follow the logs and look for these messages:
- ospd-openvas:
Finished loading VTs. The VT cache has been updated from version X to Y. - gvmd:
Updating VTs in database ... done (X VTs). - gvmd:
update_scap_end: Updating SCAP info succeeded - gvmd:
sync_cert: Updating CERT info succeeded.
docker compose -f $DOWNLOAD_DIR/compose.yaml logs -f gvmd ospd-openvas
You can also check Administration > Feed Status in the web interface once you can log in.
Step 6: Access the Greenbone Security Assistant
On the scanner itself, open:
https://127.0.0.1
The web interface now runs over HTTPS by default, and port 9392 redirects to it. The certificate is self-signed by the gvm-config container, so your browser will warn you the first time. Log in as admin with the password from step 4.
Reaching it from another machine. Most home lab scanners are headless, so you’ll want to open the interface from your laptop. The safest way is an SSH tunnel, which keeps the web interface off your network entirely:
ssh -L 8443:127.0.0.1:443 you@your-scanner
Then browse to https://127.0.0.1:8443 on your laptop.
If you really want it on the LAN, Greenbone’s workflows page shows how: set NGINX_HOST, NGINX_HTTP_PORT and NGINX_ACCESS_CONTROL_ALLOW_ORIGIN_HEADER on the gvm-config service, and change the nginx ports to 80:80 and 443:443. Do that only on a trusted network, behind your firewall, and never port forward it to the internet.
Step 7: Run your first scan
Once the feed has loaded:
- Go to Configuration > Targets and create a target with the IP address or range of a machine you own.
- Go to Scans > Tasks, create a new task, pick that target and the Full and fast scan config.
- Start the task and watch the progress bar. A single host usually takes a few minutes; a whole subnet takes much longer.
When it finishes, open the report and sort by severity. Start with anything marked high, and check whether the finding applies to the version you actually run before you act on it. If you want a second opinion, my Nessus Essentials in Docker guide sets up Tenable’s free scanner the same way, and the nmap cheat sheet helps you see which ports are open before you scan.
Keep the feed and containers up to date
Always grab the latest compose.yaml first, because Greenbone changes services between releases. Then pull and restart:
curl -f -O -L https://greenbone.github.io/docs/latest/_static/compose.yaml --output-dir "$DOWNLOAD_DIR"
docker compose -f $DOWNLOAD_DIR/compose.yaml pull
docker compose -f $DOWNLOAD_DIR/compose.yaml up -d
To refresh only the feed data:
docker compose -f $DOWNLOAD_DIR/compose.yaml pull notus-data vulnerability-tests scap-data dfn-cert-data cert-bund-data report-formats data-objects
docker compose -f $DOWNLOAD_DIR/compose.yaml up -d notus-data vulnerability-tests scap-data dfn-cert-data cert-bund-data report-formats data-objects
Don’t run greenbone-feed-sync on the host for a container install; updates come from these data images.
Managing Docker Containers
# Status of every service
docker compose -f $DOWNLOAD_DIR/compose.yaml ps
# Stop the stack but keep your data
docker compose -f $DOWNLOAD_DIR/compose.yaml down
# Start from scratch: this deletes ALL data, including scan results
docker compose -f $DOWNLOAD_DIR/compose.yaml down -v
Troubleshooting
Feed Status shows the feeds as weeks or months old. This was reported again in November 2026. Pulling fresh feed data images fixed it for the person who reported it:
docker compose -f $DOWNLOAD_DIR/compose.yaml pull notus-data vulnerability-tests scap-data dfn-cert-data cert-bund-data report-formats data-objects
docker compose -f $DOWNLOAD_DIR/compose.yaml up -d notus-data vulnerability-tests scap-data dfn-cert-data cert-bund-data report-formats data-objects
CVE data stops at an older date and gvmd logs “No JSON CPE dictionary found”. A November 2026 forum report describes the SCAP data updating while the newest CVEs in the database stayed frozen, with gvmd unable to find nvd-cpes.json (only the compressed .gz file was present). There’s no official fix yet; if you see the same log message, follow the forum thread linked in Sources before trying workarounds.
The stack doesn’t come back after a reboot. Several 2026 forum threads report containers (including nginx) not starting after the host restarts. Start them again with docker compose -f $DOWNLOAD_DIR/compose.yaml up -d, then check docker compose -f $DOWNLOAD_DIR/compose.yaml ps to confirm everything is running.
Feed status says “too old” even after an update. This usually means you’re on an old compose file that still points at the greenbone/* images on Docker Hub. Download the current compose.yaml (step 2), then pull and start again.
VTs are up to date but don’t appear in the web interface. Restart the scanner:
docker compose -f $DOWNLOAD_DIR/compose.yaml restart ospd-openvas
Port lists, scan configs or report formats are missing. Force gvmd to reload them:
docker compose -f $DOWNLOAD_DIR/compose.yaml \
exec -u gvmd gvmd gvmd --rebuild-gvmd-data=all
“Greenbone Vulnerability Manager service is not responding” at login. gvmd isn’t up. Restart it and check its logs:
docker compose -f $DOWNLOAD_DIR/compose.yaml restart gvmd
docker compose -f $DOWNLOAD_DIR/compose.yaml logs -f gvmd
Redis keeps restarting with “cannot remove ‘/run/redis/redis.sock’: Permission denied”. Recreate the socket volume, which Greenbone says is safe to remove:
docker compose -f $DOWNLOAD_DIR/compose.yaml rm -s -f redis-server ospd-openvas
docker volume rm greenbone-community-edition_redis_socket_vol
docker compose -f $DOWNLOAD_DIR/compose.yaml up -d
PostgreSQL messages like “role gvmd already exists” on start-up are harmless once the database is set up.
Keeping it safe
- Change the admin password before anything else (step 4).
- Keep the localhost binding. The first version of this guide suggested changing the port to
9392:80so anyone could reach it. Don’t: a scanner’s web interface holds a map of every weakness on your network. Use an SSH tunnel instead. - Never expose it to the internet. If you need remote access, use a VPN or an SSH tunnel.
- Scan only systems you own or have written permission to test.
- Keep it updated. Old feeds miss new vulnerabilities, and old images carry their own bugs.
- Treat reports as sensitive. Store exports somewhere private and delete ones you no longer need.
Sources
- Greenbone Community Containers (official setup guide)
- Greenbone container workflows: updates, feed sync, remote access
- Greenbone container troubleshooting
- Greenbone docs changelog
- Official compose.yaml
- Docker Engine install guide
- Greenbone forum: registry service change and supported tags, April 2026
- Greenbone forum: Community Feed coverage change, 2026
- Greenbone forum: compose file changes, February 2026
- Greenbone forum: feed status not updating, November 2026
- Greenbone forum: CVE data frozen, November 2026
- Greenbone forum: containers not starting after reboot
- gvmd on GitHub (security policy and advisories)
- Greenbone forum: feed status “too old” after following the docs
Updated 15 November 2026: rewritten for Greenbone’s current compose.yaml (new image registry, nginx with HTTPS on localhost), added password, feed, update, troubleshooting and safety steps, plus the 2026 changes: narrower Community Feed coverage, the February compose changes, the April registry tag change, and two open problems reported in November.