I think from what I’ve read that this is the case, but I’ve read some other info that’s made it less clear to me.

On the second part of the question regarding container engines, I’m pretty sure that may also be correct, and it kinda makes me wonder a little about risks of engine lock-in, but that may be a little out of scope.

  • ALostInquirer@lemm.eeOP
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    Regarding your question about lock-in, if I understand it correctly, you are targeting the kernel really, thats the “engine”. So “lock-in” is about the same as you choosing which OS to target.

    I may have been using the wrong terminology. Going off another reply here what I was referring to may also be called an orchestrator? So by this I was referring to software like Docker and possibly getting tied up in it.

    • varsock
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      I see. That’s a good question because I’m not even aware of other “orchestrators” outside of kubernetes 😅