Container entrypoint script is not executable

The application's container could not start: its entrypoint (powershell) was not found in the image, or is not executable (chmod +x). The full output is in the deploy log.

Seen8 times · 6 variants
WhereDocker Compose, Dockerfile

Why it happens

The repository commits its entrypoint script without the execute bit, and its Dockerfile copies it into the image and runs it without chmod, so the container cannot start.

What the log looks like

Deploy log
#8 0.503 runc run failed: unable to start container process: error during container init: exec: "powershell": executable file not found in $PATH#8 ERROR: process "powershell -Command iex ((new-object net.webclient).DownloadString('https://chocolatey.org/install.ps1'));     choco feature disable --name showDownloadProgress ;     choco feature enable -n allowGlobalConfirmation" did not complete successfully: exit code: 1WARNING: current commit information was not captured by the build: failed to read current commit information with git rev-parse --is-inside-work-treeDockerfile.windows:19----…

Try PanelAlpha Engine yourself.

The easiest way to turn your server into a safe, controlled environment for your AI agent. Deploy, manage and maintain any project from Claude Code, Cursor, Codex or any other MCP client. Open source under Apache 2.0, free to run.

Requires Ubuntu 24.04 or 26.04 · 2 GB RAM · 1 CPURead the documentation