| I've been running one of these for a few months too and was excited when I saw an ARMv7 CPU. In the open source and container world, many projects have stopped supporting the Zero and RPi1 due to its lack of RAM and slow CPU speed. Even running "go build" can take multiple seconds on a simple program. Starting Node.js was also fairly slow. The RPi zero shines for Python scripts that access hardware - for sensors and camera projects that are low power and cheap to make. It was actually perfect for the GrowLab project that we did over the summer with 20 others from the community https://growlab.dev - sensor data and camera images were aggregated to a more powerful RPi3/4 and then either uploaded to a static GitHub Pages site, fed into InfluxDB to create beautiful charts with Grafana. The new Zero 2 means that I can start to run ARMv7 or even ARM64 containers on the zero again, but with the limit of 512GB of RAM. The launch blog post explains why this couldn't be made higher. The first thing I tried out was not K3s, which I knew already suffers on a Raspberry Pi 3, but faasd. Faasd is OpenFaaS but built for pure containerd, no multi-node networking and no Kubernetes. It works fairly well for a few functions, even with NATS and Prometheus being deployed as part of the stack. So whilst you're not going to be building K3s clusters with these, they can run containers - with Docker, containerd, nerdctl and even as a full application stack with faasd. Where this gets more interesting for me, is hosting small applications, integrations or APIs. Perhaps with Ingress via a tunnel that can penetrate NAT/firewalls like Inlets, Argo or Ngrok. I've ordered one of the release models to see how it performs. Look out for a blog post from me soon. |