Since ArcadeDB 2026.2.1, the Docker container no longer starts with a default database graph, despite it still being configured in the gremlin-server.properties config:
gremlin.graph=com.arcadedb.gremlin.ArcadeGraph
gremlin.arcadedb.directory=./databases/graph
This is bothersome for the usage of ArcadeDB in testing scenarios, e.g. being used as a test container for integration tests of services, which use ArcadeDB as a data backend.
A current workaround is to explicitly set the default database via start command / JAVA_OPTS environment variable option:
-Darcadedb.server.defaultDatabases=graph[root:<root-password>:admin]
Explicitly defining another directory, for instance for a volume mount, also seem to work, but this is rather a production usecase:
- Start command /
JAVA_OPTS environment variable option
-Darcadedb.server.databaseDirectory=/mnt/databases
- Adjust
gremlin-server.properties config
gremlin.graph=com.arcadedb.gremlin.ArcadeGraph
gremlin.arcadedb.directory=/mnt/databases/graph
None of these workarounds should be necessary, in my opinion.
Since ArcadeDB 2026.2.1, the Docker container no longer starts with a default database
graph, despite it still being configured in thegremlin-server.propertiesconfig:This is bothersome for the usage of ArcadeDB in testing scenarios, e.g. being used as a test container for integration tests of services, which use ArcadeDB as a data backend.
A current workaround is to explicitly set the default database via start command /
JAVA_OPTSenvironment variable option:Explicitly defining another directory, for instance for a volume mount, also seem to work, but this is rather a production usecase:
JAVA_OPTSenvironment variable optiongremlin-server.propertiesconfigNone of these workarounds should be necessary, in my opinion.