Rename Docker Hub image from installer to talos-rpi5

The image supports both RPi 5 and CM5 (same SoC/RP1), so talos-rpi5
is a better public-facing name. The internal build still produces
an installer image which gets retagged to svrnty/talos-rpi5:<tag>
in the release target.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Mathias Beaulieu-Duncan 2026-02-09 18:01:00 -05:00
parent e31cd9add8
commit 19db31b717
3 changed files with 9 additions and 6 deletions

View File

@ -4,7 +4,7 @@
# Runs on ARM64 self-hosted runner (ASUS GX10) # Runs on ARM64 self-hosted runner (ASUS GX10)
# #
# Produces: # Produces:
# - Installer container image → Docker Hub (svrnty/installer:<tag>) # - Installer container image → Docker Hub (svrnty/talos-rpi5:<tag>)
# - Raw disk image → Gitea release (metal-arm64.raw.zst) # - Raw disk image → Gitea release (metal-arm64.raw.zst)
name: Build Talos CM5 Image name: Build Talos CM5 Image
@ -83,7 +83,7 @@ jobs:
## Artifacts ## Artifacts
- `metal-arm64.raw.zst` — Raw disk image for eMMC flashing - `metal-arm64.raw.zst` — Raw disk image for eMMC flashing
- `docker.io/svrnty/installer:${{ steps.version.outputs.tag }}` — Installer image for `talosctl upgrade` - `docker.io/svrnty/talos-rpi5:${{ steps.version.outputs.tag }}` — Installer image for `talosctl upgrade`
## Usage ## Usage
```bash ```bash
@ -91,7 +91,7 @@ jobs:
./scripts/flash-emmc.sh metal-arm64.raw.zst ./scripts/flash-emmc.sh metal-arm64.raw.zst
# Upgrade existing node # Upgrade existing node
talosctl upgrade --image docker.io/svrnty/installer:${{ steps.version.outputs.tag }} talosctl upgrade --image docker.io/svrnty/talos-rpi5:${{ steps.version.outputs.tag }}
``` ```
release-dir: . release-dir: .
release-notes-assistant: none release-notes-assistant: none

View File

@ -19,6 +19,9 @@ REGISTRY_USERNAME ?= svrnty
TAG ?= $(shell git describe --tags --exact-match 2>/dev/null || echo dev) TAG ?= $(shell git describe --tags --exact-match 2>/dev/null || echo dev)
# Public image name on Docker Hub (used by talosctl upgrade)
IMAGE_NAME ?= talos-rpi5
# System extensions baked into the image # System extensions baked into the image
EXTENSIONS ?= ghcr.io/siderolabs/iscsi-tools:v0.1.6 ghcr.io/siderolabs/util-linux-tools:2.40.4 EXTENSIONS ?= ghcr.io/siderolabs/iscsi-tools:v0.1.6 ghcr.io/siderolabs/util-linux-tools:2.40.4
@ -139,8 +142,8 @@ installer:
.PHONY: release .PHONY: release
release: release:
docker pull $(REGISTRY)/$(REGISTRY_USERNAME)/installer:$(TALOS_TAG) && \ docker pull $(REGISTRY)/$(REGISTRY_USERNAME)/installer:$(TALOS_TAG) && \
docker tag $(REGISTRY)/$(REGISTRY_USERNAME)/installer:$(TALOS_TAG) $(REGISTRY)/$(REGISTRY_USERNAME)/installer:$(TAG) && \ docker tag $(REGISTRY)/$(REGISTRY_USERNAME)/installer:$(TALOS_TAG) $(REGISTRY)/$(REGISTRY_USERNAME)/$(IMAGE_NAME):$(TAG) && \
docker push $(REGISTRY)/$(REGISTRY_USERNAME)/installer:$(TAG) docker push $(REGISTRY)/$(REGISTRY_USERNAME)/$(IMAGE_NAME):$(TAG)
# #
# Clean # Clean

View File

@ -6,7 +6,7 @@ The official Talos Image Factory does not support CM5 — the mainline kernel la
## What it builds ## What it builds
- **Installer image**`docker.io/svrnty/installer:<tag>` (for `talosctl upgrade`) - **Installer image**`docker.io/svrnty/talos-rpi5:<tag>` (for `talosctl upgrade`)
- **Raw disk image** → Gitea release `metal-arm64.raw.zst` (for eMMC flashing) - **Raw disk image** → Gitea release `metal-arm64.raw.zst` (for eMMC flashing)
Baked-in config: Baked-in config: