Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

jbpm container fails to start, likely permissions issue on start_jbpm-wb.sh script #64

Open
pitrh opened this issue Oct 14, 2024 · 0 comments

Comments

@pitrh
Copy link

pitrh commented Oct 14, 2024

Hi,

When deploying the "docker-compose-examples/jbpm-full-postgres-persistent.yml" sample config to a kubernetes cluster (v1.30.4), the jbpm container fails to start, leaving this message in the dashboard:

Error: failed to start container "jbpm": Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "./start_jbpm-wb.sh": stat ./start_jbpm-wb.sh: no such file or directory: unknown

As far as I can figure out, this is likely down to wrong permissions (missing execute bit, perhaps?) on the script in question.

Hopefully deploying an image with the correct permissions on the script fixes this problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant