Docker Compose containers not starting automatically after server reboot

Community Containers
1

Hello,

I am using the official OpenVAS Docker Compose configuration.

I have noticed that after rebooting the server, not all OpenVAS containers are started automatically. The containers that are missing can be started successfully by manually running docker compose up -d again.

Is this expected behavior, or is there a recommended way to ensure that all OpenVAS containers are started automatically after a server reboot?

For example, should I configure a specific Docker restart policy or use a systemd service to start the Docker Compose stack after boot?

Any recommendations for the proper setup would be appreciated.

Best regards,

2

After restart 6 containers are running. The other container like greenbone-community-edition-dfn-cert-data-1 are containers to retrieve feed updates they terminate after they have done theirs job.

3

Hello network123,
I can confirm this behavior on Docker hosts with limited resources. I wasn’t able to ensure reliable restarts using Docker restart policies. That’s why I use a cron job on the Docker host to regularly check for missing containers and restart them if necessary.
Best regards