spegel
distribution-spec
spegel | distribution-spec | |
---|---|---|
8 | 54 | |
810 | 740 | |
6.9% | 2.4% | |
9.4 | 7.8 | |
5 days ago | 7 days ago | |
Go | Go | |
MIT License | 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.
spegel
- BTFS (BitTorrent Filesystem)
-
Using ECR as a mirror to transparently proxy docker-hub when rate limited
I’m trying out spegel, so far, it’s been great
-
Constantly re-pulling the same image(s)?
As other stated, check disk space, PullPolicy etc. However, local caching can be done using tools like Spegel that makes sure each node gets all images used in the cluster for faster restarts.
-
Pull through cache, like AWS just announced
I also recently found spegel, where each Cluster Node provides its images to the other nodes: https://github.com/XenitAB/spegel
-
Docker's deleting Open Source images and here's what you need to know
https://github.com/xenitAB/spegel
I have avoided a couple of incidents caused by images being removed or momentarily not reachable with it. It would at least mitigate any immediate issues caused by images being removed from Docker Hub.
- I created Spegel to enable nodes in a cluster to pull images from each other
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
What are some alternatives?
Harbor - An open source trusted cloud native registry project that stores, signs, and scans content.
jib - 🏗 Build container images for your Java applications.
crow-registry
spin - Spin is the open source developer tool for building and running serverless applications powered by WebAssembly.
bottlerocket - An operating system designed for hosting containers
proxmox-lxc-idmapper - Proxmox unprivileged container/host uid/gid mapping syntax tool.
ipcs - containerd meets ipfs to distribute content
appleprivacyletter - An open letter against Apple's new privacy-invasive client-side content scanning.
lmctfy - lmctfy is the open source version of Google’s container stack, which provides Linux application containers.
dive - A tool for exploring each layer in a docker image
nix-portable - Nix - Static, Permissionless, Installation-free, Pre-configured
bartholomew - The Micro-CMS for WebAssembly and Spin