docker-library / docker-library/python
Cant enable and find core dumped
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 2.8k
- Forks
- 1.1k
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 1
Description
When my Python program fails in a Docker container, no core dump or backtrace is generated. I tried enabling it using ulimit -c unlimited, but it didn't help. I cannot find a stack trace to determine why my program is crashing. All I get is a corrupted size vs. prev_size message.
Contributor guide
No contributing guide indexed for this repository
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 Python crash in the Docker container and investigate why ulimit -c unlimited does not produce a core dump or backtrace. Compare the container's behavior with the expected core-dump configuration and document a reproducible path to obtain the stack trace; done when the failure can be diagnosed from the generated output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- devops, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100