Scap-data unhealthy after update

How To
1

I’m currently having an issue starting the Greenbone Community Containers after updating the feeds and containers.

Configuration:

FEED_RELEASE: "24.10"

I updated the feeds/containers and then started the Greenbone Community Edition with:

docker compose -f docker-compose.yml -p greenbone-community-edition up -d

After waiting for a while, the following errors appear:

✘ Container greenbone-community-edition-vulnerability-tests-1
  Error dependency vulnerability-tests failed to start

✘ Container greenbone-community-edition-scap-data-1
  Error dependency scap-data failed to start

dependency failed to start:
container greenbone-community-edition-scap-data-1 is unhealthy

I have repeated the update/start procedure several times, but the result is always the same. The scap-data container eventually becomes unhealthy, which prevents the dependent containers from starting correctly.

This setup was working before the update.

Could anyone please confirm whether this is a known issue with the current Greenbone Community Containers / FEED_RELEASE: "24.10"?

If additional logs or diagnostic information would be useful, I can provide them.

Thank you for your help!

2

SCAP-data unhealthy after update — !!!Issue resolved!!!

Root cause:

SCAP has now successfully finished copying the data and is “healthy.”

The issue was caused by the container health check. The initialization period was set to only 5 seconds:

start_period: 5s

This was not enough time for the SCAP feed to be copied and initialized. As a result, the container was marked as “unhealthy” even though the initialization process was still running.

Solution:

The health check start_period was increased to 15 minutes:

scap-data:
  image: registry.community.greenbone.net/community/scap-data
  healthcheck:
    start_period: 15m  // Example value. probably is 15m to long 
  environment:
    KEEP_ALIVE: 1
  volumes:
    - scap_data_vol:/mnt

Afterwards, I ran:

./restart-openvas.sh

again. This recreated the container and applied the updated setting.

Result: The SCAP feed was able to complete the copy process successfully, and the scap-data container is now correctly reported as “healthy.”

2 Likes