distribution-spec
wsl-distrod
distribution-spec | wsl-distrod | |
---|---|---|
56 | 27 | |
766 | 1,847 | |
3.4% | - | |
7.5 | 0.0 | |
17 days ago | over 1 year ago | |
Go | Rust | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
distribution-spec
-
A step-by-step guide to building an MLOps pipeline
One of the main reasons teams struggle to build and maintain their MLOps pipelines are vendor specific packaging. As a model is handed off between data science teams, app development teams, and SRE/DevOps teams, the teams are required to repackage the model to work with their unique toolset. This is tedious, and stands in contrast to well adopted development processes where teams have standardized on the use of containers to ensure that project definitions, dependencies, and artifacts are shared in a consistent format. KitOps is a robust and flexible tool that addresses these exact shortcomings in the MLOps pipeline. It packages the entire ML project in an OCI-compliant artifact called a ModelKit. It is uniquely designed with flexible development attributes to accommodate ML workflows. They present more convenient processes for ML development than DevOps pipelines. Some of these benefits include:
-
A Brief History Of Serverless
Internally, Google used a platform called Borg which is still used by Google to this day. It also served as the basis for Kubernetes. Borg is a container-based platform whose goal was to allow developers to focus on code, not infrastructure. Google has an entire infrastructure team to manage the datacenters. This system came out circa 2004. This predates the advent of modern OCI Containers by about a decade.
-
The transitory nature of MLOps: Advocating for DevOps/MLOps coalescence
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.
-
The Road To Kubernetes: How Older Technologies Add Up
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.
-
Coexistence of containers and Helm charts - OCI based registries
OCI stands for Open Container Initiative, and its goal as an organization is to define a specification for container formats and runtime.
-
Bazzite – a Steam0S-like OCI image for desktop, living room, and handheld PCs
https://opencontainers.org/
Here is Containerfile from the repo: https://github.com/ublue-os/bazzite/blob/main/Containerfile
-
Distroless images using melange and apko
apko allows us to build OCI container images from .apk packages.
- OCI image from dockerfile
- Fat OCI images are a cultural problem
-
Progressive Delivery on AKS: A Step-by-Step Guide using Flagger with Istio and FluxCD
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
wsl-distrod
-
Arch in WSL
Systemd works even in the non-store Windows 10 using https://github.com/nullpo-head/wsl-distrod
-
Should I be creating a WSL "install" for each project?
In case you're using an older version of WSL that doesn't support systemd, you can give Distrod a try.
-
Losing everything due to WSL corruption?
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.
-
wsl-archlinux-manager: An efficient & easy strategy to install and manage Arch Linux instances on WSL.
I use distrod to get a wsl instance of Arch running. It's nice to have (some) systemd functionality with it ;)
-
I finally got arch linux working on windows 11(WSL2) By using docker.
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.
-
How to install robo3t on Ubuntu WSL, Windows 11
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/.
-
Cannot install WSL UBUNTU 22 in windows 10
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.
-
WSL2 with no network connectivity
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).
-
Install minikube with podman and CRI-O on wsl2 / Windows 11
I used Distrod tool to install WSL that has extra features like systemd, auto-start and port forwarding ability.
-
Now you can even replace systemd with Emacs
https://github.com/nullpo-head/wsl-distrod I use this at work with Gentoo and it's worked fine.
What are some alternatives?
jib - 🏗 Build container images for your Java applications.
distrobox - Use any linux distribution inside your terminal. Enable both backward and forward compatibility with software and freedom to use whatever distribution you’re more comfortable with. Mirror available at: https://gitlab.com/89luca89/distrobox
spin - Spin is the open source developer tool for building and running serverless applications powered by WebAssembly.
genie - A quick way into a systemd "bottle" for WSL
proxmox-lxc-idmapper - Proxmox unprivileged container/host uid/gid mapping syntax tool.
easyWSL - Create WSL distros based on Docker Images.
appleprivacyletter - An open letter against Apple's new privacy-invasive client-side content scanning.
ArchWSL - ArchLinux based WSL Distribution. Supports multiple install.
dive - A tool for exploring each layer in a docker image
WSL2-Linux-Kernel - The source for the Linux kernel used in Windows Subsystem for Linux 2 (WSL2)
bartholomew - The Micro-CMS for WebAssembly and Spin
arch_linux_wsl2 - Installation instructions for Arch Linux in WSL2