runc
CoreDNS
runc | CoreDNS | |
---|---|---|
32 | 41 | |
11,428 | 11,800 | |
1.5% | 1.6% | |
9.3 | 9.3 | |
5 days ago | 7 days ago | |
Go | 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.
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 ?
CoreDNS
-
Small DNS Server That Support Outgoing Address Binding?
CoreDNS supports this via the bind plugin.
- The Tailscale Universal Docker Mod
-
How to use Cloudflare 1.1.1.1 with Kubernetes DNS
I'd like to use Cloudflare's 1.1.1.1 and 1.0.0.1 nameservers in Kubernetes, alongside DNS over TLS. It looks like I can do it using core-dns. I need to setup the following somehow:
-
Dockerize Bind9 DNS with custom image
Shamless plug for CoreDNS. Much better DNS server than classic bind9. And of course there's already a nice container image for it.
-
Kubernetes traffic discovery
But another approach that could work in Kubernetes, because the DNS servers are within the cluster itself, would be to work directly with the DNS server pods. In most Kubernetes clusters, whether standalone or managed (GKE, AKS, EKS), the cluster DNS is either coredns or kube-dns. That was great to minimize how much configuration options we’d need to support. We realized we could edit the coredns or kube-dns configmap resources to enable their log option, which would make them log all the queries they handle. We’ll cover exactly how it’s done in more detail below.
-
Self hosted DNS server that responds to queries with data from web API?
CoreDNS has an ectd plugin, so your service could add entries to a database, which is used as record source. Not the same mechanism as you have described, but it will get the job done. Also this is what Kubetnetes does for incluster dns records.
-
Upgrade CoreDNS without downtime and without kubernetes
nevermind there's caddy builtin upgrade method https://github.com/coredns/coredns/issues/6034
-
Guide for using DNS with home lab servers?
Coredns can be spun up in a docker container, just starting to get into it myself
-
What would you rewrite in Golang?
CoreDNS is a pretty good DNS server.
-
Cool networking projects in golang
Core DNS (https://coredns.io).
What are some alternatives?
crun - A fast and lightweight fully featured OCI runtime and C library for running containers
PowerDNS - PowerDNS Authoritative, PowerDNS Recursor, dnsdist
Moby - The Moby Project - a collaborative project for the container ecosystem to assemble container-based systems
blocky - Fast and lightweight DNS proxy as ad-blocker for local network with many features
youki - A container runtime written in Rust
Pi-hole - A black hole for Internet advertisements
podman - Podman: A tool for managing OCI containers and pods.
nsupdate.info - Dynamic DNS service
containerd - An open and reliable container runtime
etcd - Distributed reliable key-value store for the most critical data of a distributed system
conmon - An OCI container runtime monitor.
cni - Container Network Interface - networking for Linux containers