From 836ca57628fd63ea849b676f4a908b908fd55100 Mon Sep 17 00:00:00 2001 From: dependencytrack-bot <106437498+dependencytrack-bot@users.noreply.github.com> Date: Thu, 18 Jun 2026 17:58:45 +0000 Subject: [PATCH] Update config docs Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> --- docs/reference/configuration/properties.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/docs/reference/configuration/properties.md b/docs/reference/configuration/properties.md index 8752db27..3468779d 100644 --- a/docs/reference/configuration/properties.md +++ b/docs/reference/configuration/properties.md @@ -423,9 +423,19 @@ Defines the name of the data source to be used by init tasks. ## Development +**`dt.dev-services.container-reuse.enabled`** [¶](#dtdev-servicescontainer-reuseenabled){ .headerlink } + +Whether dev services containers shall be reused across restarts.

When enabled, containers are kept running when Dependency-Track stops, and re-attached to on the next start. This preserves PostgreSQL state (schema and data) across restarts and avoids the cost of re-provisioning on every run.

This additionally requires Testcontainers reuse to be opted into on the developer's machine, either via testcontainers.reuse.enable=true in the `~/.testcontainers.properties` file, or the `TESTCONTAINERS_REUSE_ENABLE=true` environment variable. Without it, this option has no effect and containers are disposed on shutdown as usual. See . + + + + + +
Typeboolean
Defaulttrue
ENVDT_DEV_SERVICES_CONTAINER_REUSE_ENABLED
+ **`dt.dev-services.enabled`** [¶](#dtdev-servicesenabled){ .headerlink } -Whether dev services shall be enabled.

When enabled, Dependency-Track will automatically launch containers for: at startup, and configures itself to use them. They are disposed when Dependency-Track stops. The containers are exposed on randomized ports, which will be logged during startup.

Trying to enable dev services in a production build will prevent the application from starting.

Note that the containers launched by the API server can not currently be discovered and re-used by other Hyades services. This is a future enhancement tracked in . +Whether dev services shall be enabled.

When enabled, Dependency-Track will automatically launch containers for: at startup, and configures itself to use them. They are disposed when Dependency-Track stops.

The port on which the frontend will be exposed is configurable via [`dt.dev-services.frontend-port`](#dtdev-servicesfrontend-port). The port of the postgres container is automatically inferred from dt.datasource.default.url.

Trying to enable dev services in a production build will prevent the application from starting.
Typeboolean