firecracker-container VS rchab

There is this project, which I have never used, but seems promising. https://github.com/firecracker-microvm/firecracker-container...

How does that compare to firecracker-containerd?

https://github.com/firecracker-microvm/firecracker-container...

This repository enables the use of a container runtime, containerd, to manage Firecracker microVMs. Like traditional containers, Firecracker microVMs offer fast start-up and shut-down and minimal overhead. Unlike traditional containers, however, they can provide an additional layer of isolation via the KVM hypervisor.

#!/bin/bash # TODO(P1, blog): Write down my experience building this for fly.io # Usage deploy_batch_job.sh scraper/fly.toml FLY_CONFIG_PATH=$1 # Set variables BASE_DOCKERFILE="/Dockerfile.base" # Here `-base-registry` is a dummy app on fly.io which is just used for storing base docker images. # You can create such a dummy app by `fly apps create $REGISTRY_DUMMY_APP_NAME` REGISTRY_DUMMY_APP_NAME="-base-registry" IMAGE_NAME="registry.fly.io/$REGISTRY_DUMMY_APP_NAME" # we do --platform linux/amd64 to match the one fly.io builders have # https://github.com/superfly/rchab/blob/8d37d90dc7d418660b50a10f288715fda4a00b5d/build.sh#L7 PLATFORM="linux/amd64" echo "Logging into fly.io registry" # Authentication successful. You can now tag and push images to registry.fly.io/{your-app} fly auth docker echo "Building batch jobs base image $DOCKERFILE ($PLATFORM) to {$IMAGE_NAME}" # Build the image locally docker build --platform $PLATFORM -t $IMAGE_NAME:latest -f $DOCKERFILE . # Get the image ID (content hash), removing the "sha256:" prefix as a IMAGE_ID=$(docker inspect --format='{{.Id}}' $IMAGE_NAME:latest | cut -d: -f2) echo "Image ID: $IMAGE_ID (content hash)" FULL_IMAGE_NAME="$IMAGE_NAME:$IMAGE_ID" # Tag the image with its content hash docker tag $IMAGE_NAME:latest $FULL_IMAGE_NAME # Check if the image already exists in the registry if docker manifest inspect $FULL_IMAGE_NAME > /dev/null 2>&1; then echo "Image $FULL_IMAGE_NAME" echo " -- already exists in the registry." echo " -- Skipping push." else echo "Pushing new image $FULL_IMAGE_NAME to the registry." docker push $IMAGE_NAME:$IMAGE_ID docker push $IMAGE_NAME:latest fi echo "Deploying the batch job $FLY_CONFIG_PATH" # To debug problems with Fly.io app builders you can find them at https://fly.io/dashboard//builders # or with CLI fly logs -a fly-builder- (get it from logs) fly deploy --config $FLY_CONFIG_PATH

Our remote builders are just fly apps based on this image with an auth proxy in front. Works great https://github.com/superfly/rchab