Skip to content

Troubleshooting

Installed with Docker

Frequently asked questions and problems that may arise when using Hummingbot with Docker:

How do I find out the name of my hummingbot instance?

Run the following command to list all docker instances you have created:

1
docker ps -a

How do I list all the containers I have created?

1
docker ps -a

How do I check that my Hummingbot instance is running?

The following command will list all currently running docker containers:

1
docker ps

How do I find out where the config and log files are on my local computer?

Run the following command to view the details of your instance:

1
docker inspect hummingbot-instance

Look for a field Mounts, which will describe where the folders are on you local machine:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
"Mounts": [
    {
        "Type": "bind",
        "Source": "/home/ubuntu/hummingbot_files/hummingbot_conf",
        "Destination": "/conf",
        "Mode": "",
        "RW": true,
        "Propagation": "rprivate"
    },
    {
        "Type": "bind",
        "Source": "/home/ubuntu/hummingbot_files/hummingbot_logs",
        "Destination": "/logs",
        "Mode": "",
        "RW": true,
        "Propagation": "rprivate"
    }
],

How do I connect to my Hummingbot instance?

1
docker attach hummingbot-instance

How do I edit the conf files or access the log files used by my docker instance?

You can access the files from your local file system, in the hummingbot_conf and hummingbot_logs folders on your machine. The docker instance reads from/writes to these local files.

Common Errors with Windows + Docker

Windows users may encounter the following error when running the Docker Toolbox for Windows:

1
2
C:\Program Files\Docker Toolbox\docker.exe: Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers).
See 'C:\Program Files\Docker Toolbox\docker.exe run --help'.

This appears to be an environment configuration problem. The solution is to refresh the environment settings and restart the environment which can be done with the following commands:

1
2
docker-machine restart default      # Restart the environment
eval $(docker-machine env default)  # Refresh your environment settings

How do I copy and paste in Docker Toolbox (Windows)?

By default, the Docker Toolbox has copy and paste disabled within the command line. This can make it difficult to port long API and wallet keys to Hummingbot. However, there is a simple fix which can be enabled as follows:

  • Open up the Docker Toolbox via the Quickstart Terminal

  • Right-click on the title bar of Toolbox and select "Properties"

  • Check the box under the "Options" tab to enable "Ctrl Key Shortcuts"

Close any warnings, and you're done! Just hit enter to move onto the next line and you should be able to copy and paste text using Ctrl+Shift+C and Ctrl+Shift+V.

How do I update Hummingbot after I had previously installed using old instructions?

If you have previously installed Hummingbot using Docker and our previous documentation naming conventions, can you copy and paste the following command to update to the latest naming as well as to enable the user scripts:

Copy the commands below and run from the root folder (i.e. when you type ls, make sure you see the my-hummingbot folder).

If your previous instance was named my-hummingbot (check by running docker ps -a):

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
# Remove instance
docker rm my-hummingbot && \
# Remove old image
docker image rm coinalpha/hummingbot:latest && \
# Rename file folder
sudo mv my-hummingbot hummingbot_files && \
# Start new instance
docker run -it \
--name hummingbot-instance \
--mount "type=bind,source=$(pwd)/hummingbot_files/hummingbot_conf,destination=/conf/" \
--mount "type=bind,source=$(pwd)/hummingbot_files/hummingbot_logs,destination=/logs/" \
coinalpha/hummingbot:latest

If your previous instance was named my-instance-1 (check by running docker ps -a):

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
# Remove instance
docker rm my-instance-1 && \
# Remove old image
docker image rm coinalpha/hummingbot:latest && \
# Rename file folder
sudo mv my-hummingbot hummingbot_files && \
# Start new instance
docker run -it \
--name hummingbot-instance \
--mount "type=bind,source=$(pwd)/hummingbot_files/hummingbot_conf,destination=/conf/" \
--mount "type=bind,source=$(pwd)/hummingbot_files/hummingbot_logs,destination=/logs/" \
coinalpha/hummingbot:latest

You will then be able to use the automated docker scripts.

Installed from source

How do I update Hummingbot?

Download the latest code from github:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
# From the hummingbot root folder:
git pull origin master

# Recompile the code:
conda deactivate
./uninstall
./clean
./install
conda activate hummingbot
./compile
bin/hummingbot.py

Alternatively, use our automated script:

1
2
3
4
# From the *root* folder:
wget https://raw.githubusercontent.com/CoinAlpha/hummingbot/development/installation/install-from-source/update.sh
chmod a+x update.sh
./update.sh

conda: not found

1
2
$ conda
-bash: conda: command not found

If you have just installed conda, close Terminal and reopen a new Terminal to update the command line's program registry.

If you use zshrc or another shell other than bash, see the note at the bottom of this section: install dependencies.

I can not start Hummingbot

Error message 1:

1
2
3
4
File "bin/hummingbot.py", line 40
  def detect_available_port(starting_port: int) -> int:
                                           ^
SyntaxError: invalid syntax

Make sure you have activated the conda environment: conda activate hummingbot.

Error message 2:

1
ModuleNotFoundError: No module named 'hummingbot.market.market_base'

Make sure you have compiled Hummingbot in the Hummingbot environment: conda activate hummingbot && ./compile.

Running Hummingbot

Coming soon.