OpenNebula VS slirp4netns

OpenNebula is a cloud computing toolkit which is used to manage heterogeneous distributed datacenter infrastructures. And it controls a data center’s virtual infrastructure to build private, public as well as hybrid implementations of IaaS.

We use opennebula: https://opennebula.io

Probably Opennubula ( https://opennebula.io/ ) will satisfy your requirements.

Have you looked at open nebula (https://opennebula.io/)? Haven't used it myself, but figured it was worth mentioning.

> ‘roll your own cloud’ is becoming more feasible

https://opennebula.io is worth looking at for that sort of thing (not that it's new). You don't have to do it that way, but its "edge" support for simple provisioning on bare metal providers doesn't include Hetzner; I think it assumes you can get instances on demand. That sort of solution isn't complex or expensive enough for my site, and doubtless others, though. Especially when you just want compute, I can't see the point in the pain (which surprised us) and expense of AWS et al.

By popular demand, we've added support for the OpenNebula cloud platform for both x86_64 and aarch64. See the OpenNebula page on the wiki for info.

History likes to repeat itself:

https://github.com/rootless-containers/slirp4netns

It should not actually require root anymore - see https://github.com/rootless-containers/slirp4netns

USER root RUN curl -o /var/lib/apt/dazzle-marks/docker.gpg -fsSL https://download.docker.com/linux/ubuntu/gpg \ && apt-key add /var/lib/apt/dazzle-marks/docker.gpg \ && add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" \ && install-packages docker-ce docker-ce-cli containerd.io RUN curl -o /usr/bin/slirp4netns -fsSL https://github.com/rootless-containers/slirp4netns/releases/download/v1.1.12/slirp4netns-$(uname -m) \ && chmod +x /usr/bin/slirp4netns

Podman pods are kind of their own thing, networking wise, being under slirp4netns https://github.com/rootless-containers/slirp4netns

i foud this slirp4netns in the meantime as well. There are a bunch of other problems. with podman. I cannot use nftables and firewalld with systemd+nftables, the mentioned port-"problem" for rootless podman, ipv6 containers and some other stuff that isn't working or very config-heavy. i found a lot of github issues that are actively discussed in the past days regarding some of the mentioned topics on this post. My conclusion is that i will still use docker and will look into this in a year or so... to early imo to really switch to podman because almost no benefits to docker for me. (i want ipv6, rootless containers all the way and full nftable support)