You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: