Update entrypoint script to ensure directory permissions for gvm

[ahmedtouahria]

What

This PR ensures that the directories /var/lib/openvas and /var/lib/gvm exist and have the correct ownership and permissions before the container drops privileges to the gvm user.

Specifically, it:

• Creates /var/lib/openvas and /var/lib/gvm if they do not exist.
• Sets ownership to gvm:gvm.
• Sets permissions to 775 to allow group write access.

This logic is executed as root before calling gosu gvm, ensuring that gvm has proper access to required lock/state directories at runtime.

The changes were verified by running the container with a fresh volume and confirming that no permission errors occur and services start normally.

Why

When running the container with fresh or mounted volumes, these directories may not exist or may be owned by root, causing permission errors when OpenVAS/GVM attempts to create lock or state files.

This leads to startup failures or unexpected behavior unless users manually create and chown these directories.

Ensuring the directories exist and are writable by gvm improves:

• Out-of-the-box usability
• Compatibility with fresh Docker volumes
• Reliability in containerized and orchestrated environments (Docker, Kubernetes, etc.)

References

N/A

Checklist

• Tests

[github-actions]

Conventional Commits Report

😢 No conventional commits found.

👉 Learn more about the conventional commits usage at Greenbone.