slimtoolkit / slimtoolkit/slim
starting container process caused "exec: \"/bin/sh\": stat /bin/sh: no such file or directory".
Open
Nobody has claimed this yet.
triage
- Dominant language
- Go
- Stars
- 23.4k
- Forks
- 840
- PR merge metrics
- No merged PRs in 30d
Description
Description
I have error after running RUN docker run -d lonly/docker-alpine-java.slim:
a26edf53fecf609b9fb93adf0880a1dc0da6f26cfe30f38041b89f651c96587e
docker: Error response from daemon: oci runtime error: container_linux.go:265: starting container process caused "exec: \"/bin/sh\": stat /bin/sh: no such file or directory".
Steps to reproduce the issue:
- RUN
docker-slim build --http-probe lonly/docker-alpine-java:oraclejre-8u152 - RUN
docker run -d lonly/docker-alpine-java.slim - See error
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 documented docker-slim build for lonly/docker-alpine-java:oraclejre-8u152, then run the resulting lonly/docker-alpine-java.slim image as shown. Compare the source and slim images to determine why /bin/sh is missing; done means the generated image starts successfully or the incompatibility is clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100