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
Currently
logbtdoes not work on AWS Fargate. The reason is thatlogbtdepends on customizing thecore_pattern, which is not possible on Fargate (you cannot modify/proc/sys/kernel/core_pattern).By design
logbtdepends 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
logbtto work on Fargate it would need to gain a mode where it can adapt to the default core_pattern on Fargate. That default iscore, which means a corefile will be dropped the current working directory of the crashing program./cc @mapsam