OpenNebula VS rootlesskit

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.

The official docs list some known limitations of rootless Docker, and says that "Host network (docker run --net=host) is also namespaced inside RootlessKit." I don't understand how RootlessKit works, but I am wondering if this means that rootless Docker containers are unable to connect to ports on the host? I also checked the RootlessKit docs but I'm out of my depth there: (https://github.com/rootless-containers/rootlesskit/blob/master/docs/network.md).

Fair Warning: If your app needs to be able to see the user's IP (for throttling, banning, etc.)

Rootless Docker doesn't properly support IPv6 yet with the ability to see the end-users source IP.

* https://github.com/rootless-containers/rootlesskit/issues/25...

There may be some overhead with networking if your application uses a very large amount of bandwidth. See:

https://github.com/rootless-containers/rootlesskit/tree/v0.1...

Otherwise for general dockerized applications, you won't notice any difference.

You may find some quirks, but these can all be worked around easily as described on the rootless docker page.

We run it in production with no issues so far.

Now with Fedora 34 I'm having issues from rootlesskit not being packaged. Got the binaries from https://github.com/rootless-containers/rootlesskit/#setup since that go get command never works. I have installed over 50 packages using go get but rootlesskit ALWAYS fails to compile because of some dependency like google/uuid and different Go versions.