Install OctoBot with Docker in video
After installation, OctoBot starts in node mode and opens its node interface. From there you can:
- Run automations configured and monitored from the new OctoBot interface or the mobile app (recommended for most users).
- Launch manual OctoBots with their own interface, deeper configuration and the backtesting engine (for expert users).
See the getting started guide for setup steps, or the connect guide if you have connection issues.
For unix distribution only
Quick install
- In a terminal, enter the command to install the necessary packages:
sudo apt install git build-essential ca-certificates curl gnupg lsb-release -y- Next, enter the command to install Docker:
curl -fsSL https://get.docker.com -o get-docker.sh
sh ./get-docker.sh- Then download the OctoBot docker-compose file:
curl -fs https://raw.githubusercontent.com/Drakkar-Software/OctoBot/master/docker-compose.yml -o docker-compose.yml- Start OctoBot with the previously downloaded docker-compose file:
docker compose up -d- Don’t forget to run the following command at the end of the installation (and logout)
sudo usermod -aG docker $USERAfter install: Initialize your OctoBot and start your first automated strategy with a risk-free virtual account.
Manual install
Using the stable image:
- Download OctoBot
docker pull drakkarsoftware/octobot:stable- Start OctoBot (for linux x64/x86 and raspberry linux arm64/arm32)
docker run -itd --name OctoBot -p 8000:8000 -p 5001-5010:5001-5010 -v $(pwd)/user:/octobot/user -v $(pwd)/tentacles:/octobot/tentacles -v $(pwd)/logs:/octobot/logs drakkarsoftware/octobot:stableAfter install: Initialize your OctoBot and start your first automated strategy with a risk-free virtual account.
Using the latest image (might be unstable):
- Download OctoBot latest
docker pull drakkarsoftware/octobot:latest- Start OctoBot (for linux x64/x86 and raspberry linux arm64/arm32)
docker run -itd --name OctoBot -p 8000:8000 -p 5001-5010:5001-5010 -v $(pwd)/user:/octobot/user -v $(pwd)/tentacles:/octobot/tentacles -v $(pwd)/logs:/octobot/logs drakkarsoftware/octobot:latestAfter install: Initialize your OctoBot and start your first automated strategy with a risk-free virtual account.
How to look at OctoBot logs ?
docker logs OctoBot -fHow to stop OctoBot ?
docker stop OctoBotHow to restart OctoBot ?
docker restart OctoBotHow to update OctoBot ?
docker pull drakkarsoftware/octobot:stable
docker stop OctoBot
docker rm OctoBot
docker run -itd --name OctoBot -p 8000:8000 -p 5001-5010:5001-5010 -v $(pwd)/user:/octobot/user -v $(pwd)/tentacles:/octobot/tentacles -v $(pwd)/logs:/octobot/logs drakkarsoftware/octobot:stableRunning with docker-compose
A simple way to run a docker image is to use docker-compose :
-
Install docker-compose
-
Download the docker-compose.yml file
-
Create a
.envfile in the current folder -
Add
HOST=YOUR_IP_ADDRESSin the newly created.envfile. (where YOUR_IP_ADDRESS is the ip address of the computer, can be replaced bylocalhostif it’s a local computer) -
Start OctoBot with docker-compose (with the previous file
docker-compose.ymlin the current folder):docker-compose up -d
After docker compose up, open the node interface at http://localhost:8000/ on the host machine (or map NODE_PORT in .env if you changed it).
After install: Initialize your OctoBot and start your first automated strategy with a risk-free virtual account.
Start multiple nodes with docker
To run a second node on the same computer, use a new container name, a new user folder, and map a different host port to 8000 (for example -p 8001:8000). Each manual OctoBot started from a node uses ports from the 5001-5010 range inside that container.
Start OctoBot with docker managed files
Warning: It’s easier to use but it will not be possible to update it without deleting its files.
-v arguments can be removed from previous start commands but OctoBot’s local files will then be managed by docker (and not directly visible).
docker run -itd --name OctoBot -p 8000:8000 drakkarsoftware/octobot:stableLocal OctoBot files path are located in /var/lib/docker and can be listed with the following command
docker inspect -f '{{ .Mounts }}' OctoBotTo copy files of a directory outside the OctoBot container, for example for logs files :
docker cp OctoBot:/octobot/logs/. .Wherer “OctoBot” is your container name
Initialize your OctoBot
After installation: Starting your OctoBot
- Open the node setupOpen
http://localhost:8000on the PC where OctoBot is running. The node setup screen opens in your browser. - Set up your node walletOn the node, create or import your node wallet to secure your node and its data. This wallet is not a cryptocurrency wallet, do not use a crypto wallet private key and never share your private key with anyone.
- Connect your Node to your OctoBot interfaceFrom the Connect your Node to your OctoBot interface step (or Settings → Connect → Web tab), open new.mobile.octobot.cloud. I already have a wallet → I already have a private key. Paste Copy your private key from this node. Then new automation → any type → Add a node → Existing install. Hostname: the hostname or IP the node shows. Port: 8000 (or what the node shows). Click Save when the checks turn green. Still Unreachable? Check our connection troubleshoot.
- Launch your first OctoBotOn new.mobile.octobot.cloud, leave demo mode on (default for risk-free simulated trading). Add an exchange account with 1000 USDC (or the crypto of your choice). Start a new automation (for example a Grid on BTC/USDC, if you added USDC to the demo account) and follow your automation from your OctoBot interface.
- Your node is now executing your strategyWhen you start an automation, the node runs it on its computer. You do not need to keep the browser tab or app open. Just leave the OctoBot program running so that it keeps trading. You can run as many automations as you want, on most crypto exchanges, with demo and real accounts. When needed, feel free to stop and restart your node, it will resume trading when you turn it back on.
Use new.mobile.octobot.cloud or the iOS or Android app on a regular basis to follow your investments and turn automations on and off. Go back to the node interface at http://localhost:8000 only for configuration, administration, or to connect to a new phone or computer.
Connection problems? Read the Node Connect Guide. If your node shows Unreachable, see connection common issues.