On Thu, Dec 5, 2024 at 11:52 PM Heidi ***@***.***> wrote: Hi there! Thank you for reaching out. I'm sorry to hear that you're encountering this error when connecting the YOLO model using Docker: exec /app/start.sh : No such file or directoryExited with code 1 This issue is commonly caused by Windows' handling of line endings in text files, which can affect scripts like start.sh used in Docker containers. To resolve this issue, please follow these steps: - *Adjust Git Configuration* Before cloning the repository, configure Git to prevent automatic conversion of line endings. Open Git Bash or your preferred terminal and run: git config --global core.autocrlf false - *Re-clone the Repository* If you've already cloned the repository, you'll need to delete your existing local copy and clone it again to ensure the line endings are preserved correctly. - Delete your existing local clone of the repository. - Run the following command to clone the repository again: git clone https://github.com/HumanSignal/label-studio-ml-backend.git - *Build and Run the Docker Containers* Navigate to the directory containing the Dockerfile and docker-compose.yml files (for the YOLO model), and then run: docker-compose build docker-compose up By following these steps, you should be able to resolve the start.sh error and successfully connect the YOLO model using Docker. For more details, please refer to the troubleshooting section in our documentation: - Label Studio ML Backend - Troubleshooting Docker Build on Windows Please let me know if you have any questions or if the issue persists. Thanks, Tyler Conlee Head of Support HumanSignal Comment by Tyler Conlee Workflow Run <https://github.com/HumanSignal/label-studio/actions/runs/12185738645> — Reply to this email directly, view it on GitHub <#6746 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BNES5BZ7P4PFKYFEBMZ3KJT2ECKW5AVCNFSM6AAAAABS5LR5NKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRRGEYTEMJUG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>