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.
TypeErrorAn error that occurred in the deployed application. It is not necessarily a PanelAlpha Engine error, but we keep working on improvements so you run into fewer of them.
Seen8 times · 6 variants
WhereDocker Compose, Dockerfile
StatusObservedOur team will look into this soon, verify the cause and try to fix it in an upcoming release.
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----…