FreeBSD Jails VS runc

You can install FreeBSD on an external disk. The FreeBSD Handbook answers the other questions. Source: 11 months ago

I have an veeery old notebook (Toshiba tecra s2) and wanted to give this machine a new life. Learning about unix and so on. Are the docs on https://docs.freebsd.org/en/books/handbook/ a good start for this? Or does someone has any recommendations? Source: about 1 year ago

In the official handbook read chapters 1-5, 13, & 19 to get oriented. Source: about 1 year ago

The system that exhibits the best software engineering in its development and in the software packaging process is undoubtedly FreeBSD -- it wouldn't hurt to look at it more carefully. I build all of my desktop (Gnome/Plasma/XFCE) and math and programming languages / editors from source code on FreeBSD using the latest stable operating system release (13.1, soon to be 13.2). See the FreeBSD Journal to get an... Source: over 1 year ago

I'd suggest not doing any searches, and just using the default documentation. The handbook is what drew me to FreeBSD nearly two decades ago. Not random documentation from different users trying to accomplish the same thing in multiple ways often with little regard to security or functionality. The Handbook isn't without flaws, but it is a excellent unified documentation that covers every basic topic. Source: over 1 year ago

It's interesting that, in light of things like this, you still see large software companies adding support for new components written in non-memory safe languages (e.g. C) As an example Red Hat OpenShift added support for crun(https://github.com/containers/crun), which is written in C as an alternative to runc, which is written in Go( - Source: Hacker News / 7 months ago

Yeah, runtimeClass lets you specify which CRI plugin you want based on what you have available. Here's an example from the containerd documentation - you could have one node that can run containers under standard runc, gvisor, kata containers, or WASM. Without runtimeClass, you'd need either some form of custom solution or four differently configured nodes to run those different runtimes. That's how krustlet did... Source: over 1 year ago

Your Docker Container can only run Linux. That's because Docker takes advantage of runC which uses the Linux kernel. You can't run Windows inside of Docker. But of course you can run Docker on a Windows host machine. If you are running a .NET project, you won't be able to use Docker. On the other hand, if you're running .NET Core then you're in luck! - Source: dev.to / over 1 year ago

This is what Podman, an open-source daemonless and rootless container engine, was developed with in mind. Podman runs using the runC container runtime process, directly on the Linux kernel, and launches containers and pods as child processes. In addition, it was developed for the Docker developer, with most commands and syntax seamlessly mirroring Docker's. Buildah, an image builder, and Skopeo, the image utility... - Source: dev.to / almost 2 years ago

If you are curious about how exactly Docker does this I urge to have a look at the following links on layered file system and the library runc and also this great wikipedia overview of Docker. - Source: dev.to / almost 2 years ago