ops-examples
runc
ops-examples | runc | |
---|---|---|
4 | 32 | |
97 | 11,441 | |
- | 0.8% | |
6.9 | 9.3 | |
about 2 months ago | 3 days ago | |
Python | Go | |
- | 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.
ops-examples
-
Nanos – A Unikernel
Yeh - we have a small language list here:
https://github.com/nanovms/ops-examples
If you're looking for a particular piece of software search on the repo first:
https://repo.ops.city/
If you don't find it and need help creating one ping me or open an issue in ops.
-
Building a unikernel that runs WebAssembly – part 1
Nanos runs not just go but pretty much any language you want to throw at it:
https://github.com/nanovms/ops-examples .
-
Running Postgres as a Unikernel
FYI, erlang && elixir workloads can run on Nanos: https://github.com/nanovms/ops-examples/tree/master/elixir .
I do understand what you are asking for though. There used to be an older project called erlang-on-xen: https://github.com/cloudozer/ling .
It'd be great to see this idea revisited although you'll need to create some sort of new handling/framework.
-
Bare Metal Racket?
See for example nanovm provides examples for a bunch of different languages, including this in Chicken Scheme https://github.com/nanovms/ops-examples/tree/master/scheme/01-hello-world ...I expect Racket would be possible too
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?
ChezScheme - Chez Scheme
crun - A fast and lightweight fully featured OCI runtime and C library for running containers
nanos - A kernel designed to run one and only one application in a virtualized environment
Moby - The Moby Project - a collaborative project for the container ecosystem to assemble container-based systems
eggos - A Go unikernel running on x86 bare metal
youki - A container runtime written in Rust
atmos - 👽 Terraform Orchestration Tool for DevOps. Keep environment configuration DRY with hierarchical imports of configurations, inheritance, and WAY more. Native support for Terraform and Helmfile.
podman - Podman: A tool for managing OCI containers and pods.
dockerops - Nanovms running in Docker x86 container for M1 Mac ARM64.
containerd - An open and reliable container runtime
OPS - ops - build and run nanos unikernels
conmon - An OCI container runtime monitor.