awesome-alternatives-in-rust
runc
Our great sponsors
| awesome-alternatives-in-rust | runc | |
|---|---|---|
| 7 | 32 | |
| 3,468 | 11,407 | |
| - | 1.4% | |
| 2.3 | 9.3 | |
| 28 days ago | 8 days ago | |
| Rust | 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.
awesome-alternatives-in-rust
-
Introducing rewriteit.net - A collection of software rewritten in Rust
I used https://github.com/TaKO8Ki/awesome-alternatives-in-rust as an initial resource. If you know of any other resources please let me know!
- Youki, a container runtime written in Rust that has passed all integration tests provided by OCI(Open Container Initiative).
- BTOP++ is a power resource monitor for Linux
- Gobang – Cross-platform TUI database management tool written in Rust
-
I recently find out this command line tool called bat, which is a cat clone and I'm blown away with it. Can you guys recommend any more of such programs?
Here's a list: https://github.com/TaKO8Ki/awesome-alternatives-in-rust
- TaKO8Ki/awesome-alternatives-in-rust
- A curated list of replacements for existing software written in Rust
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?
btop - A monitor of resources
crun - A fast and lightweight fully featured OCI runtime and C library for running containers
bpytop - Linux/OSX/FreeBSD resource monitor
Moby - The Moby Project - a collaborative project for the container ecosystem to assemble container-based systems
iotop - A top utility for IO
youki - A container runtime written in Rust
nnn - n³ The unorthodox terminal file manager
podman - Podman: A tool for managing OCI containers and pods.
modern-unix - A collection of modern/faster/saner alternatives to common unix commands.
containerd - An open and reliable container runtime
conmon - An OCI container runtime monitor.