REPLYOPSAI RESEARCH NOTE
FREQTRADE GUIDE

Freqtrade Docker Setup

Containers simplify deployment only when configuration, strategies, models and trade data survive container replacement.

What must persist

Mount the Freqtrade user-data directory outside the container. Configuration, strategies, FreqAI models and the dry-run database should not disappear when an image is upgraded or a container is recreated.

Container lifecycle vs trading state

IMAGE→CONTAINER↔PERSISTENT USER DATA

The container should be replaceable. Strategy files, configuration, model artifacts, logs and the trade database should live in persistent storage. If recreating the container erases the experiment record, the deployment boundary is wrong.

FAILURE TESTEXPECTED RESULT
Restart containerTrade state and configuration remain available
Recreate containerPersistent user data survives
Host rebootBot returns according to the chosen restart policy
Bad image/updateKnown-good version can be restored without rewriting evidence

Start with dry-run

Keep dry_run enabled while validating exchange connectivity, pair selection, strategy loading, logs and restart behavior. A container starting successfully is not evidence that a strategy is profitable.

Operational checks

  1. Pin or deliberately update the Freqtrade image version.
  2. Use a restart policy for unexpected exits and host reboots.
  3. Keep secrets out of images and public repositories.
  4. Verify mounted data after a test container replacement.
  5. Review logs and disk growth periodically.

Next

Docker solves packaging, not server security or strategy validation.

Secure the VPS →
Set up PAPER testing →