Skip to main content
Only evaluating? Demo mode runs a complete instance from a single docker run, with no database server and no setup wizard. Use this guide when you want persistent storage and real credentials.

​
Before you start

To complete this guide, you’ll need Docker Compose installed on your computer. To confirm if Docker Compose is available, run the following command:

​
Clone the setup repository

The repository contains configuration and helper scripts to help you get started.

​
Generate configuration files

In this step, you’ll generate a set of environment files that will be used to configure each of the services deployed by Docker Compose.
1

Choose your preferred database

This determines the database that Docker Compose should deploy. You don’t need an existing database.
2

Generate environment files

The following command will create a .env directory containing environment files for each Docker Compose service.

​
Deploy Databunker Pro using Docker Compose

1

Start Docker Compose services

2

Copy the access code from the logs

On first start Databunker Pro switches to installation mode and prints a one-time six-digit access code. Follow the Databunker Pro container logs to read it:
Copy the access code, then press Ctrl-C to leave the log view. This only stops following the logs — the container keeps running.
3

Access the web interface

In your browser, open localhost:3000 to access the Databunker web interface.
4

Last Step: Generate admin credentials

Continue to Generate admin credentials to submit the access code, apply a license key, and capture your root access token, wrapping key, and Shamir key shares.

​
Oracle-specific notes

If you chose the Oracle stack, a few things differ from PostgreSQL and MySQL:
  • First boot takes a few minutes while Oracle initializes — longer on Apple Silicon, where the image runs emulated. Follow the progress with ./logs.sh and wait for the access code before opening the web interface.
  • There is no separate database to create. The image auto-creates the schema user from APP_USER / APP_USER_PASSWORD inside the FREEPDB1 pluggable database, and in Oracle the schema is the namespace (ORACLE_SERVICE=FREEPDB1).
  • Passwords are short by design. Oracle limits passwords to 30 bytes and parses them as identifiers, so generate-env-files.sh produces a short, letter-initial, alphanumeric password.
  • TLS is opt-in and requires an Oracle wallet. Run ./generate-env-files.sh ssl and see docker-compose-oracle/README.md for the two-step setup.
  • ./oracle.sh opens a sqlplus session as the schema user.