Anton Whalley

Just a comment here - It was identified as this being due to bidirectional mounts which are configurable in the core-dump-handler chart.

@swermin quick update to let you know I'll get to the review over the next few days. I want to land this for the next release which I'm planning for...

Thanks for the nudge @usimd I'm external to IBM now so I've just requested @jjasghar to set me up with the right permissions to accept this. FWIW this is close...

Update - Looks like I'm back as repo admin - Thanks @jjasghar I'll look at this ASAP.

Thanks for the reminder - been very busy for the past few weeks. I'll wait to see if we can get this other one in and do a release. https://github.com/IBM/core-dump-handler/pull/162#pullrequestreview-2228995725

That sounds like an excellent feature - thanks for offering to share it back. I need to resolve a side issue with the build system as we have disabled external...

Thanks - I've merged the PR with some additional house keeping around the workflows and released into crates.io as well as tagged in the repo - https://github.com/No9/libcrio/releases/tag/v2.1.0

Hey @Robert-Stam Can you confirm which `aws.values.xxx.yaml` you have used in the deployment and which version of EKS you are using. It's likely that the version of crio is now...

I don't have access to an AWS account to debug. Can you log into an agent container that has processed a core dump and provide the output of ``` cat...

crictl is already on the host on IKS and others so it isn't a useful test. Did you look for the compose logs as per this comment? https://github.com/IBM/core-dump-handler/issues/102#issuecomment-2016027968