They are working on this aren’t they? I haven’t seen anything in their videos or blog posts, but I thought 8.3beta was going to have native docker at some point.
Guessing enterprise is mostly building a host VM for any containers that they need to deploy. While this does seem a bit “wasteful”, I also see what Olivier was getting at with security. If the container is compromised, then the DOM or XEN layers could be compromised.
It would make it easy for home lab to just blast a container up if this was native in XCP, and from my point of view, that’s what I would be looking for, ease of deployment. Guess I should stop being so lazy.
You might also want to take a look at other products that focus more on hyper-converged infrastructure and infrastructure as code, such as https://harvesterhci.io/, combined with https://www.rancher.com/, rather than using the fork of one of the oldest hypervisors around, which naturally focuses more on managing traditional VMs
EDIT: And no, as Oliver Lambert said, I wouldn’t run anything on Dom0, it’s not a good idea. If you want to run Kubernetes on XCP-ng, use multiple VMs, preferably distributed across a cluster of multiple physical hosts, otherwise what’s the point of running Kubernetes if the infrastructure you plan to run it on isn’t at least somewhat hyperconverged
I’ve been meaning to get my hands dirty with harvester. Still looks like it has a way to go though.
I’ve been using xcp-ng personally and professionally for quite some time, but it has its limitations (2TB hard disks, cannot resize disk while vm is running, proper zfs support, etc).