Docker Deployment

Docker is the simplest path for a new deployment. The CPAMP image contains Manager Server and the embedded management.html panel. CPA / CLI Proxy API is still a separate service, and can run in the same Compose stack.

For new deployments, use the Manager Server-hosted panel:

http://<host>:18317/management.html

Do not carry over the old CPA-Manager "CPA panel + External Usage Service URL" workflow. In Plus, the full feature set comes from Manager Server. CPA Panel mode only means CPA hosts the panel; it does not read Manager Server SQLite monitoring data.

Requirements

Before deployment, confirm:

• A running CPA / CLI Proxy API instance, or a plan to start CPA in the same Compose stack.
• CPA Management API enabled.
• A CPA Management Key.
• Persistent /data storage mounted and backed up.
• Exactly one CPAMP Manager Server consuming one CPA usage queue.

Recommended CPA version:

v7.1.39+

Minimum for HTTP usage queue:

v6.10.8+

CPA must allow Manager Server to access the Management API:

remote-management:
  secret-key: "your CPA Management Key"
  allow-remote: true

Request monitoring depends on CPA usage publishing:

usage-statistics-enabled: true

CPAMP can also enable this during first setup or config save.

Deploy CPA And CPAMP Together

If CPA is not running yet, start CPA and CPAMP with this Compose file:

services:
  cli-proxy-api:
    image: eceasy/cli-proxy-api:latest
    container_name: cli-proxy-api
    restart: unless-stopped
    ports:
      - "8317:8317"
    volumes:
      - cpa-data:/app/data

  cpa-manager-plus:
    image: seakee/cpa-manager-plus:latest
    container_name: cpa-manager-plus
    restart: unless-stopped
    ports:
      - "18317:18317"
    environment:
      HTTP_ADDR: "0.0.0.0:18317"
      USAGE_DB_PATH: "/data/usage.sqlite"
      CPA_MANAGER_DATA_KEY_PATH: "/data/data.key"
      # Recommended for managed deployments:
      # CPA_MANAGER_ADMIN_KEY: "replace-with-a-long-random-admin-key"
      USAGE_COLLECTOR_MODE: "auto"
      USAGE_BATCH_SIZE: "100"
      USAGE_POLL_INTERVAL_MS: "500"
      USAGE_QUERY_LIMIT: "50000"
    volumes:
      - cpa-manager-plus-data:/data
    depends_on:
      - cli-proxy-api
    healthcheck:
      test: ["CMD", "wget", "-qO-", "http://127.0.0.1:18317/health"]
      interval: 10s
      timeout: 3s
      retries: 3

volumes:
  cpa-data:
  cpa-manager-plus-data:

docker compose up -d

Open:

http://<host>:18317/management.html

On first setup, enter:

Admin Key:          cmp_admin_... from startup logs
CPA URL:            http://cli-proxy-api:8317
CPA Management Key: CPA remote-management.secret-key

If CPA_MANAGER_ADMIN_KEY is not set, CPAMP generates an admin key and prints it once in the startup log:

docker compose logs cpa-manager-plus

After setup, new browsers log in with the CPAMP Admin Key. The CPA Management Key is encrypted and stored server-side.

Deploy CPAMP Only

If CPA is already running, start only CPAMP:

docker run -d \
  --name cpa-manager-plus \
  --restart unless-stopped \
  -p 18317:18317 \
  -v cpa-manager-plus-data:/data \
  seakee/cpa-manager-plus:latest

You can also use the GHCR image:

ghcr.io/seakee/cpa-manager-plus:latest

CPA URL Examples

Scenario	CPA URL to enter during CPAMP setup
CPA and CPAMP in the same Compose network	http://cli-proxy-api:8317
CPA runs on Docker Desktop host	http://host.docker.internal:8317
CPA runs on Linux host, CPAMP in Docker	http://host.docker.internal:8317 plus --add-host=host.docker.internal:host-gateway
CPA is remote and only suitable for HTTP queue	https://your-cpa.example.com

Linux host CPA example:

docker run -d \
  --name cpa-manager-plus \
  --restart unless-stopped \
  --add-host=host.docker.internal:host-gateway \
  -p 18317:18317 \
  -v cpa-manager-plus-data:/data \
  seakee/cpa-manager-plus:latest

Then use:

http://host.docker.internal:8317

Do not use 127.0.0.1 from inside a container to reach CPA on the host. Inside the container, 127.0.0.1 means the container itself.

Common Environment Variables

Variable	Default	Description
HTTP_ADDR	0.0.0.0:18317	Manager Server listen address.
USAGE_DATA_DIR	/data	Data directory.
USAGE_DB_PATH	/data/usage.sqlite	SQLite database path.
CPA_MANAGER_DATA_KEY_PATH	/data/data.key	Data key path.
CPA_MANAGER_ADMIN_KEY	empty	Explicit Manager Server admin key.
CPA_MANAGER_ADMIN_KEY_FILE	/run/secrets/cpa_admin_key	Read the admin key from a file.
CPA_MANAGER_DATA_KEY	empty	Explicit data encryption key.
CPA_MANAGER_DATA_KEY_FILE	/run/secrets/cpa_data_key	Read the data encryption key from a file.
CPA_UPSTREAM_URL	empty	Optional environment-managed CPA URL.
CPA_MANAGEMENT_KEY	empty	Optional environment-managed CPA Management Key.
CPA_MANAGEMENT_KEY_FILE	/run/secrets/cpa_management_key	Read the CPA Management Key from a file.
USAGE_COLLECTOR_MODE	auto	auto, subscribe, http, or resp.
USAGE_BATCH_SIZE	100	Max collected records per batch.
USAGE_POLL_INTERVAL_MS	500	Idle poll interval.
USAGE_QUERY_LIMIT	50000	Max recent usage events returned.

For the full runtime reference, see Manager Server Guide.

Data Persistence And Backup

Always mount /data. Docker defaults:

/data/usage.sqlite
/data/usage.sqlite-wal
/data/usage.sqlite-shm
/data/data.key

Backups must include both SQLite files and data.key:

docker run --rm \
  -v cpa-manager-plus-data:/data \
  -v "$PWD":/backup \
  alpine \
  tar czf /backup/cpa-manager-plus-data-backup.tar.gz -C /data .

Why data.key matters:

• usage.sqlite stores usage data and encrypted CPAMP configuration.
• data.key decrypts the saved CPA Management Key.
• If data.key is lost, the saved CPA Management Key cannot be recovered; save the CPA connection again.

Collection Paths

When USAGE_COLLECTOR_MODE=auto, Manager Server tries these paths in order:

1. RESP Pub/Sub.
2. HTTP usage queue.
3. RESP pop fallback.

RESP Pub/Sub and RESP pop must connect directly to the CPA API port, usually 8317. Normal HTTP reverse proxies do not work for RESP. HTTP usage queue can go through an HTTP proxy.

If you see unsupported RESP prefix 'H', the RESP collector is probably connected to an HTTP address. Prefer auto or http, and confirm CPA is at least v6.10.8+.

Upgrade

Back up /data first.

Compose:

docker compose pull
docker compose up -d

docker run:

docker pull seakee/cpa-manager-plus:latest
docker stop cpa-manager-plus
docker rm cpa-manager-plus
docker run -d \
  --name cpa-manager-plus \
  --restart unless-stopped \
  -p 18317:18317 \
  -v cpa-manager-plus-data:/data \
  seakee/cpa-manager-plus:latest

Verification

Basic health checks:

curl http://127.0.0.1:18317/health
curl http://127.0.0.1:18317/usage-service/info

After setup, check collector status:

curl -H "Authorization: Bearer <CPAMP_ADMIN_KEY>" \
  http://127.0.0.1:18317/status

Important fields:

configured
collector.lastError
lastConsumedAt
lastInsertedAt
eventCount

If the monitoring page is empty, continue with Request Monitoring Troubleshooting.

What Changed From CPA-Manager

Old CPA-Manager Docker docs used seakee/cpa-manager and described an external Usage Service for a CPA-hosted panel. In CPA Manager Plus:

• Image is seakee/cpa-manager-plus.
• Container is usually named cpa-manager-plus.
• Full Docker / Manager Server mode login uses the CPAMP Admin Key, not the CPA Management Key.
• The CPA Management Key is encrypted with /data/data.key.
• CPA Panel mode is pure CPA-backed and does not configure external Manager Server analytics.