Koha Testing Docker on Windows WSL: Common Setup Problems and Fixes

Koha Testing Docker on WSL: Common Setup Problems and Fixes While setting up Koha Testing Docker (KTD) on Windows using WSL and Docker Desktop, I encountered several problems related to Docker configuration, port conflicts, and accessing Koha through the browser. This guide summarizes the problems I encountered, how I diagnosed them, and how I fixed them. The goal is to provide a practical troubleshooting guide for anyone setting up Koha Testing Docker on Windows with WSL and Docker Desktop. Environment My setup consisted of: Windows WSL (Ubuntu) Docker Desktop Koha Testing Docker (KTD) 1. ktd pull Could Not Find Docker Problem When I initially ran: ktd pull KTD produced an error similar to: .../ktd: line 725: /usr/bin/docker: No such file or directory At first, this was confusing because Docker was already installed and working. I checked: which docker and received: /usr/bin/docker I also ran: /usr/bin/docker --version which successfully displayed the installed Docker version. Therefore, Docker itself was not missing. Cause The problem was related to how the KTD configuration was being read. The .env file was not being interpreted correctly, and it also contained Windows-style CRLF line endings. I checked the file using: cat -v .env If the output contains ^M at the end of lines, that indicates Windows-style line endings. For example: DOCKER_BINARY=/usr/bin/docker^M The ^M is the carriage-return character from Windows line endings. Fix I made sure that .env contained: DOCKER_BINARY=/usr/bin/docker I also converted the .env file to Unix-style line endings. After fixing the configuration, I ran: ktd pull again, and it worked successfully. Lesson When using configuration files between Windows and WSL/Linux, always check for CRLF line endings if a shell script behaves unexpectedly. 2. Port 8080 Was Already in Use Problem After successfully pulling the KTD images, I tried to start the environment: ktd up -d However, Docker returned an error similar to: ports are not avai