kernel-images

Oops, I forgot to add the link: https://github.com/onkernel/kernel-images

This looks excellent, and very fun to play with! I used this one-liner to run an instance directly from remote source: dagger -c 'git https://github.com/onkernel/kernel-images | head | tree | docker-build --dockerfile containers/docker/Dockerfile | up --ports 8501:8501,8080:8080,6080:6080,9222:9222' Be aware that the initial docker build is quite long... But caching kicks in for subsequent runs. I look forward to playing with this!

We’ve been building infrastructure to spin up browsers for AI agents. Originally, we built[0] it as a pool of warm Docker containers running Chromium, exposing: - Chrome DevTools Protocol (for Playwright/Puppeteer) - noVNC (for live view) We’ve been following the unikernel space for a while, so we decided to see if we could get our image on one. We went with Unikraft Cloud[1]. Here’s how it did: - Boot-up time: 10–20ms (vs. ~5s for Docker containers) - Near 0 CPU/memory consumption when idle - Still ~8GB RAM when active (headful Chromium) Potential use cases: - Standby mode during long-running jobs: unikernels can sleep after X sec of inactivity, reducing clock time costs - Session reuse: auth/session cookies persist for hours/days. Basically as long as the cookies are valid - Cold start speed: good for low-latency, event-based handling W