Explore supporting AWS Fargate
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 25
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Currently `logbt` does not work on AWS Fargate. The reason is that `logbt` depends on customizing the `core_pattern`, which is not possible on Fargate (you cannot modify `/proc/sys/kernel/core_pattern`).
By design `logbt` depends on a customized pattern of `/tmp/logbt-coredumps/core.%p.%E`. This enables a reliable location to retrieve core dumps that is cleanly named by the PID (%p) and the crashing program (%E).
So, for a future version of `logbt` to work on Fargate it would need to gain a mode where it can adapt to the default core_pattern on Fargate. That default is `core`, which means a corefile will be dropped the current working directory of the crashing program.
/cc @mapsam
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
Review how logbt configures core_pattern and locates core dumps, then compare that flow with AWS Fargate's default core pattern of `core`. Done means logbt has a defined mode for Fargate that can find and process the core file in the crashing program's current working directory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, shell
- Domain
- cloud, operating-systems, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100