Unstructured-IO / Unstructured-IO/unstructured-api
Running unstructured-api docker image in openshift result in permission denied
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 951
- Forks
- 192
- Avg merge
- 7d 8h
- Merged PRs (30d)
- 2
Description
I used openshift to deploy unstructured-api creates following error: level=error msg="runc create failed: unable to start container process: exec: "scripts/app-start.sh": stat scripts/app-start.sh: permission denied"
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the OpenShift deployment of the unstructured-api Docker image and inspect the container entrypoint at scripts/app-start.sh. Verify the cause of the permission-denied error and define completion as a container that starts successfully in OpenShift without this error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python, shell
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100