I'm curious - can you please share a bit of details on how Docker complicates debug and recovery of an OOM-killed process (be it ES or anything else - personall

I'm curious - can you please share a bit of details on how Docker complicates debug and recovery of an OOM-killed process (be it ES or anything else - personally, I have Redis in mind)? I've assumed it's almost no different from non-isolated case. If the container dies - it would just get to "stopped" state and can be restarted. Exactly the same as if process had died and I run it again, except for process is wrapped. And if all the non-ephemeral data process writes goes to host-mounted directories ("volume"), then a container can be safely discarded as it's nothing but read-only layers. Guess, I just don't see something because I haven't yet got bitten. (I never used Docker besides toy/tiny stuff, but considering its images as a sort of quick-and-dirty good-enough packaging system - just because proper .debs would take much more time and effort to produce and maintain. So, really curious about hearing the possible drawbacks I don't know yet.) Thanks!