Core dump. How to get it to stop?

My homeassistant installation (docker container based) dumps a core file almost on a weekly base. I haven’t noticed HA being unavailable, which means it recovers from this crash. But I would like to get rid of it, preferably the good way, i.e. have the bug that causes it fixed, or prevent the core from being stored on disk. I am running on a media that I would prefer not to receive that much data due to wear and backup reasons. The core is the main python process (easily checked with file core), but I also looked at it with gdb but as I didn’t have python3.13 installed outside the container (and it isn’t available or so it appears), I just got to see a corrupted stack (bt command).

Would creating a folder called core in the config folder prevent this dump? I think I will do just that, but if the crash is to be fixed, what information should I post? I do not know what triggers the crash.

Read the homeassistant.log.1 file in the config folder.
It is the log file from the previous run, ie. the one up to the crash.

Seems to be the homeassistant.log.fault file that gets the crash log appended every time. Unfortunately not timestamped, but I can see that HA crashed just 2 minutes after I started it by looking at the timestamps:

-rw------- 1 root root 747839488 Jun 28 17:09 homeassistant/config/core
-rw-r–r-- 1 root root 167832518 Jun 28 17:07 homeassistant/config/home-assistant.log.1
-rw-r–r-- 1 root root 691870 Jun 28 17:09 homeassistant/config/home-assistant.log.fault

The fault file has 36 crash dumps in it.

Hello Bernhard,