runtime VS gvisor

Let me give you an example. [Here's one of the best questions I've ever asked on the internet.]https://github.com/kata-containers/runtime/issues/2795) I've seen many better questions asked, but this is the best I've been able to manage. I provided a decent description of the problem, a test-case that allowed other people to reproduce it as well (not relevant in your case), what I tried that didn't work, and the exact log messages and system information that indicated the problem. I then followed up with the people who were helping me and the problem was resolved.

in parts of prod we use a combination of cgroups (mentioned in the thread already), taskset https://man7.org/linux/man-pages/man1/taskset.1.html, and in other cases (HPC workloads on large clusters) Kata Containers to isolate and optimize application resources: https://katacontainers.io/

It might use a hypervisor though, as the pendulum swings back

https://katacontainers.io/

Kata Containers

Isn't gVisor kind of this as well?

"gVisor is an application kernel for containers. It limits the host kernel surface accessible to the application while still giving the application access to all the features it expects. Unlike most kernels, gVisor does not assume or require a fixed set of physical resources; instead, it leverages existing host kernel functionality and runs as a normal process. In other words, gVisor implements Linux by way of Linux."

https://github.com/google/gvisor

This sort of feels like seeing someone riding a bike and saying: why don’t they just get a car? The simple fact is that containers and VMs are quite different. Whether something uses VMX and friends or not is also a red herring, as gVisor also “rolls it own VMM” [1].

[1] https://github.com/google/gvisor/tree/master/pkg/sentry/plat...

There's two major production-ready Go-based operating system(-ish) projects:

- Google's gVisor[1] (a re-implementation of a significant subset of the Linux syscall ABI for isolation, also mentioned in the article)

- USBArmory's Tamago[2] (a single-threaded bare-metal Go runtime for SOCs)

Both of these are security-focused with a clear trade off: sacrifice some performance for memory safe and excellent readability (and auditability). I feel like that's the sweet spot for low-level Go - projects that need memory safety but would rather trade some performance for simplicity.

[1]: https://github.com/google/gvisor

[2]: https://github.com/usbarmory/tamago

It uses gVisor to create a TCP/IP stack in userspace, and starts a wireguard interface on it, which the HTTP server from http.Serve listens on. The library will print a URL after startup, where you can access your server. You can create multiple listeners in one binary.

The playground compiles the program with GOOS=linux, GOARCH=amd64 and runs the program with gVisor. Detailed documentation is available at the gVisor site.

You could use a container sandbox like gVisor, light virtual machines as containers (Kata containers, firecracker + containerd) or full virtual machines (virtlet as a CRI).