Docker compose "init: true" causes container start failure
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.2k
- Forks
- 692
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
After installing updates today, I am unable to get any Compose stack that uses "init: true" to launch properly. They start but fail with "exec /sbin/docker-init: no such file or directory".
Reproduction steps
- "docker compose up" on any stack with "init: true"
Expected behavior
The stack comes up and functions properly.
Additional context
I have also tested using just a standard "docker run --init" and it fails as well. i.e., "docker run --init nginx:1-alpine"
I have tested manually setting the init-path and forcing "init: true"
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 failure with docker compose up and docker run --init nginx:1-alpine, then compare the behavior with the manually set init-path and forced init: true cases. Trace why /sbin/docker-init is unavailable; done means stacks using init: true start and function normally.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100