title: Analyze container file system on kubernetes after it exits/crashes
body: <p>Perhaps a silly question with no sense:</p>
  
  <p>In a kubernetes deployment (or minikube), when a pod container crashes, i would like to analyze the file system at that moment. In this way, i could see core dumps or any other useful information.</p>
  
  <p>I know that i could mount a volume or PVC to get core dumps from a host-defined core pattern location, and i also could get logs by mean a rsyslog sidecar or any other way, but i still would like to do "post-mortem" analysis if possible. I assume that kubernetes should provide (but i don't know how, that's the reason of my question) some mechanism to do this forensics tasks easing the life to all of us, because in a production system we could need to analyze killed/exited containers.</p>
  
  <p>I tried playing directly with <em>docker run</em> without <em>--rm</em> option, but can't get nothing useful from inspection to get useful information or recreate the file system in last moment that had the container alive.</p>
  
  <p>Thank u very much!</p>