3 ms·

I can't say I've ever cared about live forking a container (or VM, for that matter)

• hinkley 1y ago
  Your cloud provider may be doing it for you. Ops informed me one day that AWS was pushing out a critical security update to their host OS. So of course I asked if that meant I needed to redeploy our cluster, and they responded no, and in fact they had already pushed it. Our cluster keeps stats on when processes start. So we can alert on crashes, and because new processes (cold JIT) can skew the response numbers, and are inflection points to analyze performance improvements or regressions. There were no restarts that morning. So they pulled the tablecloth out from under us. TIL.
  • mort96 1y ago
    None of this is making live forking a container desirable to me, I'm not a cloud hosting company (and if I was, I'd be happy to provide a VPS as a VM rather than a container)
    • hinkley 1y ago
      There’s using a feature, having a vendor use it for you, or denying its worth. Anything else is dissonant.
      • mort96 1y ago
        For the VM case, I'm sure I might have benefited from it, if Digital Ocean have been able to patch something live without restarting my VPS. Great. Nothing I need to care about, so I have never cared about live forking a VM. It hasn't come up in my use of VMs. It's not a feature I miss in containers, is what I'm saying.