I've seen it, and I've also seen it in Kubernetes.
It's obviously not the intended use case, but it can have the advantage of plugging in much nicer with your existing tooling.
As an example, if I have a Kubernetes cluster, and a new app that needs a full VM.
My options are to containerize it (it likely already comes this way), and let Kubernetes scheduled it on it's own VM, or use a different tool in order to manage the unique VM for this app.
Unless there are reasons to avoid the containerize approach, I'm going to stick with the existing tooling rather than add additional complexity.
Most cases I've seen the apps don't need more than a two dozen megabytes out of the gigabytes in the VM. It was crazy seeing how much resources were being wasted for no good reason.
It's obviously not the intended use case, but it can have the advantage of plugging in much nicer with your existing tooling.
As an example, if I have a Kubernetes cluster, and a new app that needs a full VM.
My options are to containerize it (it likely already comes this way), and let Kubernetes scheduled it on it's own VM, or use a different tool in order to manage the unique VM for this app.
Unless there are reasons to avoid the containerize approach, I'm going to stick with the existing tooling rather than add additional complexity.