Docker / Instant Evaluation

Exaba ships a Docker image, exaba/exaba on Docker Hub, so you can evaluate the S3 API, the web console, and the IAM flow on a single host in minutes.

Evaluation only. The Docker image is for evaluation and development, not production. It is pre-release software, and the on-disk format may change between versions, which can lose previously written data. For production, see Production Installation.

Quick start

# Pull the image
docker pull exaba/exaba:latest

# Generate an admin password and note it down (the container does not print it)
ADMIN_PASSWORD="$(openssl rand -base64 24)"
echo "Admin password: $ADMIN_PASSWORD"

# Run it: accept the EULA, set the admin user, and auto-provision a cluster
docker run \
  -p 9000:9000 \
  -p 9006:9006 \
  -e EULA=y \
  -e ADMIN_USER=admin \
  -e ADMIN_PASSWORD="$ADMIN_PASSWORD" \
  exaba/exaba:latest

CLUSTER_NAME and CLUSTER_GB auto-provision a ready-to-use cluster on startup, so the S3 endpoint is usable immediately with no manual cluster setup. Sign in to the web console as the admin user with the password printed above.

Once it is running:

  • S3 endpoint: http://localhost:9000
  • Web console: http://localhost:9006

The container is ephemeral by default; restarts lose data unless you mount a host directory at /data (add -v /data:/data to the run command).

The Docker Hub page is the official, always-current reference for the image, its tags, and run options.

Ports

PortService
9000S3 object endpoint
9006Web console / admin UI

Docker image environment variables

These variables configure the eval container at startup:

VariableRequiredPurpose
EULARequiredAccept the licence terms. Set to y to start the container.
ADMIN_USERRequiredUsername for the initial administrator account.
ADMIN_PASSWORDRequiredPassword for the initial administrator account. Generate a strong value, for example openssl rand -base64 24.
CLUSTER_NAMEOptionalName of the cluster to auto-provision at startup. Set together with CLUSTER_GB for a ready-to-use cluster.
CLUSTER_GBOptionalCapacity in gigabytes to provision for the auto-created cluster.
S3_URLOptionalExternal S3 endpoint URL that clients should use, for example http://s3.example.com:9000.

How Exaba configuration works

Beyond the image variables above, Exaba services are configured through environment variables that follow a consistent pattern:

EXABA_<SERVICE>_<SECTION>_<KEY>
  • <SERVICE> is the component, for example MAXIO (object storage), KMS, IAM, DNS, or SYNC.
  • <SECTION>_<KEY> maps to a setting in that service’s configuration file. For example, EXABA_MAXIO_STORAGE_<KEY> overrides the matching key in the [Storage] section of the MaxIO configuration.
  • Names are uppercase, and an environment variable overrides the value set in the config file.
  • List values are comma-separated.

Most evaluations need only the image variables above; the EXABA_ variables are for advanced tuning.

See also