This page contains a list of common errors and how to solve them.

If you have any technical questions or problems please ask them in the tech-support discord channel.

My bot keeps folding even though I didn't code that?

It is possible that your bot failed to build or connect to the engine. The engine is programmed in a way that your bot will still run but will only post blinds, if possible check and otherwise fold. Check for errors in the logs of the engine like "Timed out waiting for cpp to connect".

If your bot ran out of time (STARTING_GAME_CLOCK is set to 60s accumulated over 1000 rounds) it will automatically post blinds and check if possible but otherwise fold.

Problems with docker

Some changes to my .env file do not have an effect when running with docker in VS Code terminals? Changing the PLAYER1_PATH, PLAYER1_PORT etc. variables that are used in compose.yaml does not have an effect when running docker compose up --build in a VS Code terminal.

Quick fix: Try to open a new VS Code terminal. In general: This will NOT occur if you run docker compose in a terminal outside of VS Code!

The root of this problem is described here: https://stackoverflow.com/a/78517796/8657837:

• The VS Code python extension automatically sets environment variables from the .env file when starting a new terminal. They are not updated if you update your .env file!
• The shell environment variables take precedence over variables defined in .env when running docker compose for variables used in the compose.yaml. This means that changing your .env file does not have an effect on variables like the player path and port.
• To make matters worse: the updated variables are actually passed on to the engine container, e.g. bot names will be updated correctly. Same goes for ports which means that the ports from the engine and the bots will be out of sync and the engine will fail to connect.
• Therefore, you could also reconfigure the python.env setting to avoid the Python extension to not load the .env file by default.

Changes to my bots code do not have an effect when running with docker?

Did you rebuild your images with docker compose build or docker compose up --build?

player1-1 Waiting to connect to engine:3001; [Errno 111] Connection refused

If the engine responds with "player_1 connected successfully" later down the line you can ignore this warning. This is simply a race condition where the engine is started after the bots. If there are errors afterwards make sure that DOCKERIZE_BOTS=true (otherwise the engine will try to find the bot path locally in its container to build and run them but the bots do not exist in that container).

Timed out waiting for player1 to connect

Ensure that DOCKERIZE_BOTS=false if you start the engine with python engine/engine.py (otherwise the engine expects the bots to be started as "stand-alone" processes). On the other hand, make sure that DOCKERIZE_BOTS=true if you start the engine with docker compose up (otherwise the engine will try to find the bot path locally in its container to build and run them but the bots do not exist in that container).

failed to solve: failed to read dockerfile: open /var/lib/docker/tmp/buildkit-mountxxxxxx/Dockerfile: no such file or directory You didn't add a Dockerfile to your bot. Please look at the skeleton bots for examples.

C++ build fails

If you get an error like this:

> [player2 4/5] RUN ["bash", "build.sh"]:
0.308 build.sh: line 2: $'\\r': command not found
" does not exist.: The source directory "/app/build
0.317 Specify --help for usage, or press the help button on the CMake GUI.
0.319 build.sh: line 6: $'make\\r': command not found
0.320 build.sh: line 7: cd: $'..\\r': No such file or directory

Then the line endings of the build.sh file of your bot need to be in unix-style (CR). You can change this easily in VS Code bottom right from CRLF.

If you get:

exec ./run.sh: no such file or directory

Then the line endings of the run.sh file of your bot need to be in unix-style (CR). You can change this easily in VS Code bottom right from CRLF.

Otherwise make sure you have the correct versions of the libraries installed. Also, try deleting the build directory to clear the cache.