Does DBeaver manage Docker Compose containers for Database Projects?

DBeaver’s Database Projects feature stores connection configurations, SQL scripts, and project metadata in a folder that can be exported and imported across teams. The goal is to use that project definition as the single source of truth for a repeatable development database environment, including container startup and teardown.

In DBeaver 24.x, project export packages configuration files only and does not create or configure underlying database instances. There is no native Docker Compose integration for starting, stopping, or destroying containers from within the IDE. A community plugin exists but is unofficial and may not remain compatible with current releases.

Can DBeaver launch or terminate Docker Compose services directly from a Database Project, or must container lifecycle management remain entirely external? If native support is not planned, what is the supported way to version-control project metadata alongside container definitions without introducing environment-specific paths?