Run Podman in such a way that it has access to system coredumps
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 11
- Forks
- 39
- Avg merge
- 18d 18h
- Merged PRs (30d)
- 1
Description
I'm having an issue with createrepo_c 1.0 crashing with segmentation fault during tests. Unfortunately I can't really utilize the coredumps to debug.
The coredump appears when I run coredumpctl on my host machine, but my host machine doesn't have the debug symbols to make the dump useful.
The container on the other hand doesn't have the ability to access the coredump on the host.
There are guides like this for making it work
https://dev.to/mizutani/how-to-get-core-file-of-segmentation-fault-process-in-docker-22ii
https://serverfault.com/questions/1143055/how-to-check-core-dump-inside-a-podman-container
The overall gist is that the container needs loosened security restrictions. Possibly this is something that we wouldn't want to enable all the time, but make it easy to enable when needed?
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 file, test, or entry point is named. Start by reviewing how this repository invokes Podman and compare the required host coredump access with the linked guides; define whether a debug-only option is acceptable and how it can be verified.
Written by the indexing model from the issue text.
Assessment
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100