wsl-distrod VS distribution-spec

Systemd works even in the non-store Windows 10 using https://github.com/nullpo-head/wsl-distrod

In case you're using an older version of WSL that doesn't support systemd, you can give Distrod a try.

It uses snapd (so in turn, systemd) so maybe that's what you missed. Up until the WSL update that brought systemd support I've been using distrod to have systemd in my WSL2 distros so it went all smoothly for me.

I use distrod to get a wsl instance of Arch running. It's nice to have (some) systemd functionality with it ;)

You don't need Docker Desktop to install Linux distros as your WSL2 systems. For Arch there's https://github.com/yuk7/ArchWSL and if you want systemd too then use this one instead https://github.com/nullpo-head/wsl-distrod/ (not specific to just Arch). Also any OCI compliant rootfs tarball goes really, you can use Docker or Podman to export images as tarballs & import them as WSL distros and vice versa. Just telling in case all you want is a distro and not a container engine like Docker running.

You can install the snap version if you have snap running (duh) so, I recommend you to either add systemd to your Ubuntu or make a new Ubuntu installation, both with this one: https://github.com/nullpo-head/wsl-distrod/.

Not sure on the specifics for why it won’t install for you, but I’d recommend trying a tool called distrod regardless. You can get Ubuntu Jammy with it and it makes the distro support systemd.

Install the resolvconf package and write the nameserver etc lines into /etc/resolvconf/resolv.conf.d/base file instead (or depending on your needs, use systemd by using a tool like Distrod and edit /etc/systemd/resolved.conf instead).

I used Distrod tool to install WSL that has extra features like systemd, auto-start and port forwarding ability.

https://github.com/nullpo-head/wsl-distrod I use this at work with Gentoo and it's worked fine.

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