exec /entrypoint.sh: no such file or directory

[yidasanqian]

use docker compose:

services:
  copilot-api:
    build: .
    ports:
      - "4141:4141"
    environment:
      - GH_TOKEN=ghu_XXXX
    volumes:
      - ./copilot-data:/root/.local/share/copilot-api
    restart: unless-stopped

Unable to start, how to fix?

[billxc]

Rootcause:
When shell scripts are created or edited on Windows, they default to CRLF (Carriage Return + Line Feed, \r\n) line endings. When the shebang line #!/bin/sh contains a \r character, the Linux kernel interprets it as part of the interpreter path (/bin/sh\r), which doesn't exist. This causes the "no such file or directory" error even though the file itself is present in the container.

I have created a to fix this issue #138

To quick fix this on your machine:

1. Open a powershell window from the project root
2. run the following command:

$content = Get-Content -Path ".\entrypoint.sh" -Raw; $content = $content -replace "`r`n", "`n"; [System.IO.File]::WriteAllText("$PWD\entrypoint.sh", $content)

[yidasanqian]

Rootcause:  根本原因（Rootcause）： When shell scripts are created or edited on Windows, they default to CRLF (Carriage Return + Line Feed, \r\n) line endings. When the shebang line #!/bin/sh contains a \r character, the Linux kernel interprets it as part of the interpreter path (/bin/sh\r), which doesn't exist. This causes the "no such file or directory" error even though the file itself is present in the container.在 Windows 上创建或编辑 shell 脚本时，它们的默认行结束格式是 CRLF（回车 + 换行，即 \r\n ）。如果 shebang 行（ #!/bin/sh ）中包含了 \r 字符，Linux 内核会将其误认为是解释器路径的一部分（ /bin/sh\r ），但实际上这个路径并不存在。因此，即使文件确实存在于容器中，也会出现“文件或目录不存在”的错误。

I have created a to fix this issue #138

To quick fix this on your machine:

1. Open a powershell window from the project root
2. run the following command:

$content = Get-Content -Path ".\entrypoint.sh" -Raw; $content = $content -replace "rn", "`n"; [System.IO.File]::WriteAllText("$PWD\entrypoint.sh", $content)

Rebuilt it, and it succeeded.