# Scap-data unhealthy after update

**URL:** <https://forum.greenbone.net/t/scap-data-unhealthy-after-update/22521>\
**Category:** How To\
**Created:** [September 29, 2026, 9:20am UTC](https://forum.greenbone.net/t/scap-data-unhealthy-after-update/22521 "2026-09-29T09:20:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![yoo](https://forum.greenbone.net/letter_avatar/yoo/32/6_449c533f586939b6e5f246632a46421f.png) [@yoo](https://forum.greenbone.net/u/yoo)\
**Post date:** [September 29, 2026, 9:20am UTC](https://forum.greenbone.net/t/scap-data-unhealthy-after-update/22521/1 "2026-09-29T09:20:15Z")

</div>

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

**Configuration:**

```auto
FEED_RELEASE: "24.10"

```

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

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

```

After waiting for a while, the following errors appear:

```auto
✘ 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!

---

<div class="post-metadata">

**Author:** ![yoo](https://forum.greenbone.net/letter_avatar/yoo/32/6_449c533f586939b6e5f246632a46421f.png) [@yoo](https://forum.greenbone.net/u/yoo)\
**Post date:** [September 30, 2026, 7:27am UTC](https://forum.greenbone.net/t/scap-data-unhealthy-after-update/22521/2 "2026-09-30T07:27:31Z")

</div>

### 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** :

```auto
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** :

```auto
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:

```auto
./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.”**
