runj VS distribution-spec

a couple projects underway for containers, still wip but promising.

https://hackmd.io/7BIT_khIRQyPAe4EdiigHg

https://github.com/samuelkarp/runj

> it's a shame that docker is built around linux

There is some interesting work happening to get an OCI-compatible runtime working

https://github.com/samuelkarp/runj

So somebody else created runj (runj is an experimental, proof-of-concept OCI-compatible runtime for FreeBSD jails.) https://github.com/samuelkarp/runj

Shout out to https://github.com/samuelkarp/runj which aims to provide OCI compatible runtime for FreeBSD jails. We are working on a Jails based sandbox implementation for running OCaml builds on FreeBSD, https://github.com/ocurrent/obuilder. If runj gets more support then it would be a good alternative to the various iocage/ezjail/etc solutions or the raw Jails implementation we have right now.

If you want to get a little more bleeding edge, follow along with samuelkarp/runj project which attempts to get docker images running via runj/containerd

containerd only runs on FreeBSD with the help of a shim to use [runj](https://github.com/samuelkarp/runj) as a backend for running the actual jails containers.

> VM's disk is a zfs filesystem on the host, it makes snapshotting (edit- ok maybe not, see below) and managing it super easy!

I think you mean that it's a ZFS volume? Although it should be possible to export a filesystem to a guest over NFS (or I guess 9p), but I haven't run into a lot of discussion or gotten around to testing it myself...

> It would be really cool if there were tools that brought them in line with docker, in terms of easy deployment and provisioning of new jails/vms. If I didn't have so many damn project ideas already...

My dream would be to see https://github.com/samuelkarp/runj polished and docker+containerd+runj made to work as the way to run the docker frontend with jails as the backend.

https://github.com/samuelkarp/runj is a proof of concept.

Pull up your sleeves and start committing

Experimental FreeBSD on FreeBSD OCI containers with runj

Back in 2013, a little company called Docker made it really easy to start using containers to package up applications. A big key to their success was the OCI (you can learn about that here), an industry wide initiative to have standards around how we package up our applications. Because of OCI standards, we have hundreds (maybe thousands?) of tools that can be combined to manage and deploy applications. So why aren’t we using this for packaging up Notebooks and AI models as well? It would make deploying, sharing, and managing our models easier for everyone involved.

Kubernetes on the backend used to utilize docker for much of its container runtime solutions. One of the modular features of Kubernetes is the ability to utilize a Container Runtime Interface or CRI. The problem was that Docker didn't really meet the spec properly and they had to maintain a shim to translate properly. Instead users could utilize the popular containerd or cri-o runtimes. These follow the Open Container Initiative or OCI's guidelines on container formats.

OCI stands for Open Container Initiative, and its goal as an organization is to define a specification for container formats and runtime.

https://opencontainers.org/

Here is Containerfile from the repo: https://github.com/ublue-os/bazzite/blob/main/Containerfile

apko allows us to build OCI container images from .apk packages.

Flagger's load testing service can be installed via a Kustomization resource based on manifests packaged as an artifact in an Open Container Initiative (OCI) registry

CRI-O is a lightweight container runtime for Kubernetes. It is an implementation of Kubernetes CRI to use Open Container Initiative (OCI) compatible runtimes for running pods. It supports runc and Kata Containers as the container runtimes, but any OCI-compatible runtime can be integrated.

So somebody else created runj (runj is an experimental, proof-of-concept OCI-compatible runtime for FreeBSD jails.) https://github.com/samuelkarp/runj