distribution-spec
proxmox-lxc-idmapper
Our great sponsors
distribution-spec | proxmox-lxc-idmapper | |
---|---|---|
54 | 15 | |
735 | 215 | |
4.1% | - | |
7.8 | 0.0 | |
6 days ago | 2 months ago | |
Go | Python | |
Apache License 2.0 | - |
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
-
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
-
Creating Kubernetes Cluster With CRI-O
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.
-
What is the current status of Docker and how far is it from getting ported?
So somebody else created runj (runj is an experimental, proof-of-concept OCI-compatible runtime for FreeBSD jails.) https://github.com/samuelkarp/runj
proxmox-lxc-idmapper
-
Docker in Privileged vs Unprivileged LXCs, AppArmor issue?
I found this helpful: https://github.com/ddimick/proxmox-lxc-idmapper
- ZFS, Media, and Virtual Machines, and shared data
- Is there a "Standard" or "Best Practice" for setting up storage in Proxmox?
-
Enabling Intel QSV for Jellyfin Docker image inside of LXC on Proxmox 7.3.6
But anyway I found beautiful script to calculate lxc.idmap https://github.com/ddimick/proxmox-lxc-idmapper after i have been brainwashing for hour why the hell VM is not starting and only getting errors from not correct intervals in .idmap.
-
Mount Point permissions on multiple LXC containers
There is an explanation and some guidance here, but the syntax is a bit difficult and I usually use this tool to help with that. It isn’t perfect but does the job in most situations.
- Problems mounting host storage to unprivileged container
- Shared storage across multiple LXC without permission issues?
- 2 LXC containers with the same shared bind mounts.
-
USB SSD Passthrough to CT
It doesn’t look like it’s being maintained, but I’ve used this helper script with success.
-
Getting the most of Proxmox VE and ZFS
You won't solve by just using the same uids/gids between the container and host, if using an unprivileged container. You'll also need to map the host/container uids/gids to one another. I think I read https://pve.proxmox.com/wiki/Unprivileged_LXC_containers until my eyeballs bled trying to wrap my head around the mapping syntax. https://github.com/ddimick/proxmox-lxc-idmapper might help, too.
What are some alternatives?
jib - 🏗 Build container images for your Java applications.
containerd - An open and reliable container runtime
spin - Spin is the open source developer tool for building and running serverless applications powered by WebAssembly.
Code-Server - VS Code in the browser
dive - A tool for exploring each layer in a docker image
rclone - "rsync for cloud storage" - Google Drive, S3, Dropbox, Backblaze B2, One Drive, Swift, Hubic, Wasabi, Google Cloud Storage, Yandex Files
appleprivacyletter - An open letter against Apple's new privacy-invasive client-side content scanning.
proxmox-lxc-idmapper - Proxmox unprivileged container/host uid/gid mapping syntax tool.
bartholomew - The Micro-CMS for WebAssembly and Spin
runc - CLI tool for spawning and running containers according to the OCI specification
skopeo - Work with remote images registries - retrieving information, images, signing content