nanos
ferros
Our great sponsors
nanos | ferros | |
---|---|---|
27 | 9 | |
2,463 | 101 | |
12.7% | 2.0% | |
9.3 | 0.0 | |
1 day ago | 9 months ago | |
C | Rust | |
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.
nanos
-
Nanos – A Unikernel
I am a bit confused, there are three sites:
And I am not sure what "thing" I am using. Is there some disambiguation? I know is OPS is the orchestration CLI, but I am confused at the difference between Nanos and NanoVMs. What should I call the section of my README that deals with this tech? Currently gone with Nanos/OPS but I am confused.
-
Kolibri OS: fits on a floppy disk, programmed using interrupts
I work with https://nanos.org && https://ops.city - we can run thousands of these on commodity hardware.
-
Mirage – A programming framework for building type-safe, modular systems
Unik was just a build tool that utilized other projects like Rump, Mirage, IncludeOS, etc. It's now dead since Solo pivoted a very long time ago to service mesh/api gateways.
The GoRump port they use was from us and then we realized we needed to code our own from the ground up for many reasons so we wrote https://nanos.org (runs as a go unikernel in GCP).
-
Building a unikernel that runs WebAssembly – part 1
A couple unikernel projects that caught my eye in the past may be of interest to you. I have no experience with them, so I can't speak to their quality though.
- Build Your Own Docker with Linux Namespaces, Cgroups, and Chroot
-
Running Postgres as a Unikernel
Definitely agree with the top part, however, I should note that, ops, the tool's, whole existence is to create disk images and upload them to any cloud, any hypervisor.
In particular, both https://ops.city && https://nanos.org are Go unikernels running on GCP and their deploys take just a few seconds to push out. AWS can be even faster cause we skip the s3 upload part. We also have lots of people using Azure which would be utilizing vhdx.
- Ask HN: Resources for Building a Webserver in C?
- A kernel designed to run only one application in a virtualized environment
-
Applications available in unikernels?
I'm with that organization that works on https://nanos.org and https://ops.city . If you aren't a software engineer but still would like to use unikernels you're in luck - we also have a package repository at https://repo.ops.city/ (running as a go unikernel on GCP) that will allow you to run and deploy pre-made applications. If you don't see something that you'd like to us there's also a way of importing docker containers into unikernels via ops which works for most (but not all) applications.
-
Ask HN: Software with biggest potential for positive impact in 5 years?
I think Unikernels like NanoVMs (https://nanos.org/) will become more important. They are more efficient and more secure than than full operating systems. Right now, I think there are no good monitoring solutions available (or at least I am not aware of any). You can't just ssh to your server, so if something goes wrong, it can be hard to debug. And they are certainly not integrated into bigger monitoring solutions like Dynatrace. But once the infrastructure is available, I would expect a large percentage of Linux servers to be replaced with unikernels.
ferros
-
Unix-like OS in Rust inspired by xv6-riscv
My company, https://www.auxon.io. We created https://github.com/auxoncorp/ferros originally to enable a customer project early in the company's life cycle.
Some time later we had another customer interested in using it and having us add some features to it (e.g. some device drivers and a persistence layer utilizing https://docs.rs/tickv/latest/tickv/). It was becoming a massive pain in the neck to work out source code sharing agreements with them, so we decided to just open source it.
There are quite a number of things that we would do differently if we had to build it again, and at some point will likely do that work to revise it. The biggest one of those is root task synthesis. The other is to build and bring in facilities for running tasks that are compiled to WASM.
-
Writing an OS in Rust to run on RISC-V
When we add WASM support to https://github.com/auxoncorp/ferros it'll sorta be like what you're angling at there in your description.
-
My Fear of Commitment to the First CPU Core
We've built things on seL4 (https://github.com/auxoncorp/ferros). We like to joke that it's the most perfect piece of nearly featureless software ever made.
There's... A LOT... of work to do before seL4 is going to be anywhere near usability parity with something like Linux, unfortunately.
Rather than make a general purpose OS, we decided to use it more like a unikernel or "library OS" where you're trying to make a well defined kind of "appliance" image to deploy to specific hardware rather than try to fake being a POSIX-y shaped OS.
-
FerrOS: Rust-y unikernels on seL4
For what it's worth, here's FerrOS's repo as well as the underlying selfe repo
-
Tokio Console
That's basically what we did with https://github.com/auxoncorp/ferros, Bundle Rust programs together as tasks to run atop the formally verified seL4 microkernel.
-
Hubris – An OS from Oxide Computer
We also built a Rust framework called FerrOS (https://github.com/auxoncorp/ferros) atop the formally-verified seL4 microkernel.
It has a similar set of usage idioms to Hubris it looks like in terms of trying to setup as much as possible ahead of time to assemble what's kind of an application specific operating system where everything your use case needs is assembled at build-time as a bunch of communicating tasks running on seL4.
We recently added a concise little persistence interface that pulls in TicKV (https://docs.tockos.org/tickv/index.html) from the Tock project you referenced above, and some provisions are being added for some more dynamic task handling based on some asks from an automotive OEM.
-
Genode – Sculpt Operating System 21.10
We built a thing to enable combining Rust applications together to be hosted on the seL4 microkernel. The developer experience is more akin to that of something like an RTOS where the OS and your applications are built and deployed together. The whole premise of it is decidedly non-POSIX-like. The current point is for assembling software for use-case-specific/appliance computing, not general purpose computing. (https://github.com/auxoncorp/ferros)
We're looking both for contributors and also actively hiring for a couple engineering positions for the above and for or mainline product.
-
OSv Unikernel – Optimizing Guest OS to Run Stateless and Serverless Apps
I tried and failed to bring unikernels to my former work when I was at Visa. Specifically, LING.
At my current company, Auxon, we recently open sourced[1] some work we did a couple years back which is more or less an attempt at the basic foundations for blending the seL4 microkernel with fairly normal no_std Rust application development and assembling them all together to make a purpose built OS/application to deploy directly to hardware or within a VM. We have some work to do to keep building it up as a foundation for broader use, but we're looking into partnering with the seL4 Foundation (now under the Linux Foundation) to iterate on it further with some of our other mutual partners. The developer experience is much closer to that of developing for an RTOS than it is like typical general purpose computing development.
I'm of course biased, but I think there's a lot of room to innovate in the space of use case specific software stacks where the domain and constraints are well understood and too many degrees of freedom are actually a hindrance and a liability, not an advantage.
-
Open sourced: Easier builds and stronger types for seL4 with Rust
On top of that is ferros (no relation to to ferrous-systems), a higher-level userland of unreasonably strong types for compile-time resource tracking. No more discovering you need more memory, or capability slots or IPC rights at runtime. These types help you fit the right seL4 screw to the right seL4 screwdriver.
What are some alternatives?
unikraft - A next-generation cloud native kernel designed to unlock best-in-class performance, security primitives and efficiency savings.
hubris - A lightweight, memory-protected, message-passing kernel for deeply embedded systems.
rusty-hermit - Hermit for Rust. [Moved to: https://github.com/hermit-os/hermit-rs]
Trusted-CGI - Lightweight runner for lambda functions/apps in CGI like mode
OPS - ops - build and run nanos unikernels
rust - Empowering everyone to build reliable and efficient software.
linuxkit - A toolkit for building secure, portable and lean operating systems for containers
tracing - Application level tracing for Rust.
unik - The Unikernel & MicroVM Compilation and Deployment Platform
console - a debugger for async rust!
dark - Darklang main repo, including language, backend, and infra