AWS Bottlerocket support about core-dump-handler HOT 4 CLOSED

Hey @psact Thanks for the letting us know about this variant.
It's important for the project that we capture these scenarios.

Looks like an additional values override would cover this?
Something called values.aws.bottlerocket.yaml stored in https://github.com/IBM/core-dump-handler/tree/main/charts/core-dump-handler and containing the variables you set.

Also update the table in the chart README and we are good to go.
https://github.com/IBM/core-dump-handler/blob/main/charts/core-dump-handler/README.md#installing-the-chart

Edit:
As an aside I'm not sure how that is working for you as it seems to be setting the core dump location to be the docker socket?
If the change is to support a different container socket in CRIO I would have expected a change to be at .Values.daemonset.crioEndpoint

from core-dump-handler.

I had set crioEndpoint: "unix:///run/dockershim.sock", and deployCrioConfig: true which seemed to work. I kept the default dump mount location at /var/mnt/core-dump-handler

I went ahead and added some parameters for mounting the host docker socket, and pushed to my branch.

https://github.com/psact/core-dump-handler/tree/bottlerocket-dockersock

I can open a PR if you would like.

from core-dump-handler.

Ah now I understand - Thanks for clarifying and putting together the yaml file.
Happy to take this as a PR

from core-dump-handler.

Fixed in V8.6.1
Thanks again for the PR

from core-dump-handler.