Upstream First
Every image extends an official upstream. solera only adds the justified delta.
Runtime service images — upstream maturity plus the justified delta.
solera curates the runtime side of the ecosystem — what lamina is to build, solera is to run.
The complement of lamina's catalog-not-runtime: lamina = build, solera = run.
Every image extends an official upstream. solera only adds the justified delta.
solera images are k8s-consumed runtime services, not build-stage donors.
Each image adds exactly what the upstream lacks. Zero-delta layers are inadmissible.
Two classes: upstream-extension and from-source (missing-platform builds).
| Image | Upstream / base | Delta | Capabilities | Platform |
|---|---|---|---|---|
| wordpress-fpm | wordpress:6.9.4-php8.3-fpm | gmp + wordpress-media.ini (uploads/memory/time tuned for media). | php-fpm · wordpress · media-optimized | linux/amd64 · linux/arm64 |
| aralez | rust:1.88-slim-bookworm → debian:bookworm-slim | ARM64-only build of upstream sadoyan/aralez. LTO disabled to fit BuildKit runner memory. | reverse-proxy · tls-termination · pingora-0.8 | linux/arm64 |
| fip-controller | rust:1.88-slim-bookworm → debian:bookworm-slim | In-tree FIP controller binary, lean runtime. | floating-ip · k8s-operator | linux/arm64 · linux/amd64 |
| fip-alias-agent | debian:bookworm-slim | iproute2 only. DaemonSet companion to fip-controller (bind FIP aliases per node). | cluster-agent · floating-ip-bind | linux/arm64 · linux/amd64 |
Three columns gate admission: what upstream provides, what we add, what we refuse to add.
Base-layer responsibilities. Patches and capabilities tracked from upstream's release cadence.
Minimum diff that turns an upstream into an ecosystem-ready service.
Held out to preserve operator override and prevent application-state leakage.
A Spiral tension is a polarity to navigate, not a problem to solve.
Pinned tags only. Bump deliberately. Never :latest in cluster manifests.
# Build & push the full catalog just build-all just push-all # Single-image build via lian-build (the same orchestrator lamina uses) just build wordpress-fpm
# Deployment snippet — wordpress-fpm image: reg.librecloud.online/solera/wordpress-fpm:6.9.4-php8.3 env: - name: WORDPRESS_DB_HOST value: mariadb.svc.cluster.local:3306 # DaemonSet snippet — fip-alias-agent image: reg.librecloud.online/solera/fip-alias-agent:0.1.0 securityContext: capabilities: add: ["NET_ADMIN"] hostNetwork: true
solera is one of four projects in tetra-build.
Every solera image is produced via lian-build. solera supplies the what; lian-build executes the how.
More information → The compute behind every solera build — the claim-arbitration fleet reached through lian-build's 'fleet adapter.
The build-time sibling: lamina caches the toolchain and pre-cooks deps so solera's from-source images don't re-install rustup on every build.
More information →Sporadic updates about solera. Double opt-in, one-click unsubscribe.