wikinewsfeed
DISCONTINUED
init-snapshot
Our great sponsors
wikinewsfeed | init-snapshot | |
---|---|---|
6 | 5 | |
23 | 240 | |
- | 0.0% | |
7.4 | 0.0 | |
about 2 years ago | almost 3 years ago | |
Go | Rust | |
GNU Affero General Public License v3.0 | MIT License |
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.
wikinewsfeed
-
Fly.io: The Reclaimer of Heroku's Magic
i'm running https://wikinewsfeed.org on fly.io
very satisfied so far and would definitely deploy there more!
one thing i don't really like about fly.io is they charge money for free Let's Encrypt SSL certs
init-snapshot
-
Firecracker internals: deep dive inside the technology powering AWS Lambda(2021)
At CodeSandbox we use Firecracker to run our VMs (more info here: https://codesandbox.io/blog/how-we-clone-a-running-vm-in-2-s...).
To answer the questions:
> what version of the kernel do you use (the github page says 5.10 but isn't that quite old?)
Right, they have tested with 5.10, but it also works with higher kernel versions. Our host currently runs 5.19 and we're planning to upgrade to 6.1 soon. The guest runs 5.15.63, we use a config very similar to the recommended config by FC team (it's in the FC repo). It's important to mention that we had to disable async pagefaulting (a KVM feature) with more modern kernel versions, as VMs could get stuck waiting for an PF resolve.
> What do you use to build the 'micro' images
We created a CLI that creates a rootfs from a Docker image. It pulls the image, creates a container and then extracts the fs from it to an ext4 disk. For the init, we forked the open sourced init from the Fly team (https://github.com/superfly/init-snapshot) and changed/added some functionality.
> How do you keep timesync of you're not using a timesync daemon?
IIRC we expose the time as a PTP device (handled by kvm) and run phc2sys to sync the time in an interval. Firecracker has some documentation on this, where it recommends chrony. It can also be done with vsock, but it would be more manual.
> Handle kernel and app logs without adding an log daemon, and same through vsocks, etc?
The init forwards stdout/stderr of the command it runs to its own stdout, which Firecracker then logs out by itself. A supervisor reads these and writes the logs to files.
-
Fly.io: The Reclaimer of Heroku's Magic
Unless they’ve changed things, there is no containerization within the VM a la kata. They run their own custom init inside the VM and use it to start the entry point. https://github.com/superfly/init-snapshot is the source.
-
Docker without Docker
Jerome wrote our init in Rust, and, after being cajoled by Josh Triplett, [we released the code (https://github.com/superfly/init-snapshot), which you can go read.
What are some alternatives?
nixpacks - App source + Nix packages + Docker = Image
image-spec - OCI Image Format
go-clean-architecture-web-application-boilerplate - A web application boilerplate built with go and clean architecture.
postgres_key_value - Key-Value storage for Posgresql in Ruby
cloud-hypervisor - A Virtual Machine Monitor for modern Cloud workloads. Features include CPU, memory and device hotplug, support for running Windows and Linux guests, device offload with vhost-user and a minimal compact footprint. Written in Rust with a strong focus on security.
gotway - ☸️ Cloud native API Gateway powered with in-redis cache
containerd - An open and reliable container runtime
gofeed - Parse RSS, Atom and JSON feeds in Go
Golang API Starter Kit - Go Server/API boilerplate using best practices DDD CQRS ES gRPC
flintlock - Lock, Stock, and Two Smoking MicroVMs. Create and manage the lifecycle of MicroVMs backed by containerd.
bocker - Docker implemented in around 100 lines of bash