Docker ospd-openvas not starting at boot

Community Containers
1

Hello,
I installed Greenbone Community Containers on Ubuntu 24.04, I setup SSL/TLS for GSA and everything works good.
After server reboot container starts automatically but looks ospd-openvas not starting, below message found in logs:
gvmd-1 | md manage:WARNING:2025-02-19 09h23.09 utc:89: osp_scanner_feed_version: failed to connect to /run/ospd/ospd-openvas.sock

Running command “docker compose ps” I can see below services running and looks greenbone-community-edition-ospd-openvas-1 is missing:

greenbone-community-edition-gsa-1
greenbone-community-edition-gvmd-1
greenbone-community-edition-openvas-1
greenbone-community-edition-openvasd-1
greenbone-community-edition-pg-gvm-1
greenbone-community-edition-redis-server-1

Running Container restart “docker compose -f $DOWNLOAD_DIR/docker-compose.yml up -d” all services starts including community-edition-ospd-openvas-1

greenbone-community-edition-gsa-1
greenbone-community-edition-gvmd-1
greenbone-community-edition-openvas-1
greenbone-community-edition-openvasd-1
greenbone-community-edition-ospd-openvas-1
greenbone-community-edition-pg-gvm-1
greenbone-community-edition-redis-server-1

Is it possible to set greenbone-community-edition-ospd-openvas-1 to start on server boot?

Thank you.

2

I think you can use scheduled bash script to verify that the containers are all up and running after a reboot and/or restart them after the boot process has completed. Otherwise, maybe competition for system resources during the boot that cause this issue since they always seem to come up for me when rebooting a VM with the containers installed on them.