Unstructured-IO / Unstructured-IO/unstructured-api
Entrypoint error when running app-start.sh
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 951
- Forks
- 192
- Avg merge
- 7d 8h
- Merged PRs (30d)
- 2
Description
Describe the bug
Getting the following error when trying to run app-start.sh:
env: can't execute 'bash
': No such file or directory
Looks like it is coming from here:
https://github.com/Unstructured-IO/unstructured-api/blob/2a0f3b7fa0966747b965afea15ec7f71b88b118a/scripts/app-start.sh#L1
To Reproduce
Tag: 0.0.80
Build Dockerfile: make docker-build.sh
note: had to modify because there is a \r line separator that needs to be removed. Check for this in app-start.sh, but doesn't seem to be the issue.
Start app: make docker-start-api
Get error:
': No such file or directory
Note: Also entered container with make docker-start-bash and ran scripts/app-start.sh with same error.
Environment:
- Build Env: Windows 11, MINGW64 terminal; Also tested on WSL2 Ubuntu with same results
Additional context
I see a similar issue #261 referencing a whitespace, but that is not present here.
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 with scripts/app-start.sh, especially line 1, and reproduce the failure using make docker-build.sh, make docker-start-api, or make docker-start-bash at tag 0.0.80. Check the script's line endings and entrypoint handling; done means app-start.sh executes successfully inside the container without the reported env error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, docker, shell
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100