Skip to content

docker.md

Latest commit

 

History

History
87 lines (58 loc) · 1.83 KB

docker.md

File metadata and controls

87 lines (58 loc) · 1.83 KB

Docker Build and Shipping

DEXBot2 now ships container images only for release tags matching v*.*.*.

Published image tags

  • latest - most recent stable release build (not updated for pre-release tags)
  • vX.Y.Z - release tag image
  • sha-<commit> - immutable commit build

Images are published to:

ghcr.io/froooze/dexbot2

Local build

docker build -t dexbot2:local .
docker run --rm -it dexbot2:local node dexbot.js help

Secure startup

For production and best secret hygiene without PM2, use the bundled unlock launcher:

node unlock-start
  • Enter the master password once interactively.
  • Password stays in daemon memory (RAM) and is not stored in .env.
  • Bot processes request private keys through the daemon socket.
  • If the credential daemon stops, rerun the launcher to unlock it again.

To start only one bot:

node unlock-start <bot-name>

For claw-only workflows that only need credentials, use:

node unlock-start --claw-only

For PM2-managed credential-daemon-only startup:

node pm2 claw-only

Run with Docker Compose

  1. Create a .env file in the project root for non-secret Docker Compose runtime values:
BOT_NAME=my-bot
RUN_LOOP_MS=5000
  1. Start the bot:
docker compose up

This compose mode runs dexbot.js directly and may prompt for the master password.

  1. View logs:
docker compose logs -f dexbot
  1. Stop:
docker compose down

Notes

  • Persist bot state/config by mounting ./profiles:/app/profiles.
  • Keep .env for non-sensitive runtime values (for example BOT_NAME, RUN_LOOP_MS).
  • Do not store the master password in .env. The secure launchers prompt once and keep it only in process memory.
  • If you prefer immutable pinning, replace latest in docker-compose.yml with a sha-<commit> tag.