[Bug]: arm64 docker run Exited (139）
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 8.8k
- Forks
- 491
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 49
Description
When Docker is running on an arm64 architecture machine, it fails to start properly with the error Exited (139), regardless of whether it is version 2.68.0 or 2.70.0
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
No files, tests, or entry points are identified in the report. Start by reproducing the Docker run failure on an arm64 machine with versions 2.68.0 and 2.70.0, then inspect the container output and architecture-specific configuration. Done means the arm64 image starts successfully without exiting with code 139.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100