community
runc
community | runc | |
---|---|---|
44 | 32 | |
11,714 | 11,441 | |
1.0% | 0.8% | |
9.7 | 9.3 | |
4 days ago | 4 days ago | |
Jupyter Notebook | Go | |
Apache License 2.0 | 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.
community
-
Complexity by Simplicity - A Deep Dive Into Kubernetes Components
Multiple container runtimes are supported, like conatinerd, cri-o, or other CRI compliant runtimes.
- Development in horizontal pod autoscaler
-
A Comprehensive Guide to API Gateways, Kubernetes Gateways, and Service Meshes
More recently, the Kubernetes SIG Network has been evolving the Gateway API to support service meshes.
-
What Rust can learn from Kubernetes governance?
https://github.com/kubernetes/kubernetes https://www.kubernetes.dev/resources/calendar/ https://github.com/kubernetes/community/blob/master/governance.md https://github.com/kubernetes/steering https://github.com/kubernetes/community/blob/master/sig-list.md
-
How Kubernetes computes CPU utilization for HPA?
According to this doc it takes the average of CPU utilization of a pod (average across the last 1 minute) divided by the CPU requested by the pod. Then it computes the arithmetic mean of all the pods' CPU.
-
How to get the resource usage of a pod in Kubernetes?
metrics-server has not supported kubectl top Resource Metrics API
-
Comparing Kubernetes Gateway and Ingress APIs
With the Gateway API being a superset of the Ingress API, it might make sense to consolidate both. Thanks to the SIG Network community, Gateway API is still growing and will soon be production ready.
-
How to get a head start into contributing to open source projects
Projects in/around Kubernetes and the CNCF are generally where I spend what little time I can these days. Most communities are incredibly welcoming and provide timely feedback. But the problem space of "managing a cloud platform" can take several years to really wrap ones head around, setting aside focused topics via SIGs like networking, storage, observability, API design, etc.
-
Getting started with kubectl plugins
Krew is a plugin manager maintained by the Kubernetes Special Interest Group (SIG) CLI community. Krew makes it easy to use kubectl plugins and helps you discover, install, and manage them on your machine. It is similar to tools like apt, dnf, or brew. Today, over 200 kubectl plugins are available on Krew - and that number is only increasing. Some projects are actively used and some get deprecated over time, but are still accessible via Krew.
-
Daily General Discussion - December 2, 2022
[1] https://k8s.devstats.cncf.io/d/9/companies-table?orgId=1&var-period_name=Last%20decade&var-metric=contributions [2] https://kubernetes.io/releases/release/ [3] https://github.com/kubernetes/community/blob/master/governance.md [4] https://github.com/kubernetes/community/blob/master/sig-list.md
runc
-
Nanos – A Unikernel
I can speak to this. Containers, and by extension k8s, break a well known security boundary that has existed for a very long time - whether you are using a real (hardware) server or a virtual machine on the cloud if you pop that instance/server generally speaking you only have access to that server. Yeh, you might find a db config with connection details if you landed on say a web app host but in general you still have to work to start popping the next N servers.
That's not the case when you are running in k8s and the last container breakout was just announced ~1 month ago: https://github.com/opencontainers/runc/security/advisories/G... .
At the end of the day it is simply not a security boundary. It can solve other problems but not security ones.
- Several container breakouts due to internally leaked fds
- Container breakout through process.cwd trickery and leaked fds
-
US Cybersecurity: The Urgent Need for Memory Safety in Software Products
It's interesting that, in light of things like this, you still see large software companies adding support for new components written in non-memory safe languages (e.g. C)
As an example Red Hat OpenShift added support for crun(https://github.com/containers/crun) this year(https://cloud.redhat.com/blog/whats-new-in-red-hat-openshift...), which is written in C as an alternative to runc, which is written in Go(https://github.com/opencontainers/runc)...
-
Run Firefox on ChromeOS
Rabbit hole indeed. That wasn't related to my job at the time, lol. The job change came with a company-provided computer and that put an end to the tinkering.
BTW, I found my hacks to make runc run on Chromebook: https://github.com/opencontainers/runc/compare/main...gabrys...
-
Crun: Fast and lightweight OCI runtime and C library for running containers
being the main author of crun, I can clarify that statement: I am not a fan of Go _for this particular use case_.
Using C instead of Go avoided a bunch of the workarounds that exists in runc to workaround the Go runtime, e.g. https://github.com/opencontainers/runc/blob/main/libcontaine...
-
Best virtualization solution with Ubuntu 22.04
runc
-
Bringing Memory Safety to sudo and su - with Ferrous Systems and Tweedegolf
Not OP, but if I had to guess, a lot of this can be picked up by just observing common security issues in the Linux space, since similar mistakes and oversights have caused quite a few real-world CVEs in the past, e.g. this random example of a TOCTTOU vulnerability in runc.
- Containers - entre historia y runtimes
- [email protected]+incompatible with ubuntu 22.04 on arm64 ?
What are some alternatives?
textbook-curriculum - Ada Developers Academy Online Curriculum
crun - A fast and lightweight fully featured OCI runtime and C library for running containers
mentoring - 👩🏿🎓👨🏽🎓👩🏻🎓CNCF Mentoring: LFX Mentorship + Summer of Code
Moby - The Moby Project - a collaborative project for the container ecosystem to assemble container-based systems
website - Kubernetes website and documentation repo:
youki - A container runtime written in Rust
cni - Container Network Interface - networking for Linux containers
podman - Podman: A tool for managing OCI containers and pods.
spec - Container Storage Interface (CSI) Specification.
containerd - An open and reliable container runtime
cri-api - Container Runtime Interface (CRI) – a plugin interface which enables kubelet to use a wide variety of container runtimes.
conmon - An OCI container runtime monitor.