1a3e551a33
Bump to Talos v1.12.3 / pkgs v1.12.0
...
Patches may need rebasing — will verify on first build.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-09 18:17:19 -05:00
bff5ca242b
Add upstream RPi5 patches from talos-rpi5/talos-builder
...
- pkgs patch: switches kernel source to RPi downstream (stable_20250428),
adds CM5/RP1 kernel config options
- talos patch: updates arm64 module list for RPi kernel modules
Source: https://github.com/talos-rpi5/talos-builder
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-09 18:08:43 -05:00
0d4f4cc50f
Use org-level REGISTRY_USERNAME/REGISTRY_PASSWORD secrets
...
Replace DOCKERHUB_USERNAME/DOCKERHUB_TOKEN with the existing org-level
secrets. Use automatic GITHUB_TOKEN for Gitea release creation.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-09 18:03:12 -05:00
19db31b717
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>
2026-02-09 18:01:00 -05:00
e31cd9add8
Initial commit: Talos CM5 builder with Gitea CI/CD
...
Custom Talos Linux image builder for Raspberry Pi CM5 on Compute Blade
hardware. Uses RPi downstream kernel (via talos-rpi5/talos-builder patches)
since the mainline kernel lacks CM5 device trees and RP1 driver support.
- Makefile: build orchestration targeting docker.io/svrnty registry
- Build pipeline: tag-triggered Gitea Actions workflow
- Update checker: weekly cron for Talos + RPi kernel releases
- CM5 overclock config: 2.6GHz (arm_freq=2600)
- Extensions: iscsi-tools, util-linux-tools
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-09 17:58:17 -05:00
