lfg2025/archy
1
0
Fork 0
Code Issues 20 Pull Requests 1 Actions Packages Projects Releases 61 Wiki Activity
archy/image-recipe/_archived
History
archipelago 6dcdada371
Some checks failed
Demo images / Build & push demo images (push) Failing after 1m36s
Details
fix(iso): make baseline apps work on a fresh install with no internet 
Fresh offline installs came up without fedimint-clientd and filebrowser
(they only appeared after connecting internet). Three root causes:

- archipelago-load-images.service ran 'podman load' as root, but every
  container runs rootless as archipelago — bundled images landed in
  root's storage where the rootless runtime can't see them, so all
  container creation silently depended on registry pulls. The loader now
  loads into the archipelago user's storage (with linger + runtime-dir
  wait + system migrate).
- The unbundled ISO bundled only filebrowser.tar; fmcd (fedimint-clientd)
  is a baseline first-boot app too and is now part of the unbundled core
  bundle.
- first-boot's pull_with_fallback always hit the network; it now uses an
  already-loaded local image first and skips the pull entirely.

Also: fedimint-clientd added to the UI's hardcoded curated-app fallback
list (it was missing when all catalog fetches fail offline), plus its
INSTALLED_ALIASES entry, and the stale fmcd bundling comment in
image-versions.sh corrected.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-16 07:31:28 -04:00
..
.gitea-workflows
chore: purge retired git.tx1138.com registry host from the codebase
2026-07-10 18:55:32 +01:00
branding
chore(release): archive ISO build recipes, tarball-only releases
2026-04-23 15:36:00 -04:00
scripts
chore(release): archive ISO build recipes, tarball-only releases
2026-04-23 15:36:00 -04:00
build-auto-installer-iso.sh
fix(iso): make baseline apps work on a fresh install with no internet
2026-07-16 07:31:28 -04:00
BUILD-ISO-STATUS.md
chore(release): archive ISO build recipes, tarball-only releases
2026-04-23 15:36:00 -04:00
build-unbundled-iso.sh
chore(release): archive ISO build recipes, tarball-only releases
2026-04-23 15:36:00 -04:00
ISO-BUILD-CHECKLIST.md
chore(release): archive ISO build recipes, tarball-only releases
2026-04-23 15:36:00 -04:00
README.md
chore(release): archive ISO build recipes, tarball-only releases
2026-04-23 15:36:00 -04:00
test-iso-qemu.sh
chore(release): archive ISO build recipes, tarball-only releases
2026-04-23 15:36:00 -04:00

README.md

Archived ISO build recipes

These scripts built the Archipelago auto-installer ISO (bundled and unbundled variants). As of v1.7.43-alpha, ISOs are no longer part of the release deliverable. Releases ship as tarballs consumed by scripts/self-update.sh on existing nodes.

Archived here rather than deleted so they can be resurrected if ISO distribution is reintroduced.

Contents

  • build-auto-installer-iso.sh — orchestrator, bundles container images into squashfs
  • build-unbundled-iso.sh — thin wrapper that sets BUNDLE_IMAGES=0 and delegates
  • test-iso-qemu.sh — smoke-tests a built ISO under QEMU
  • scripts/convert-iso-to-disk.sh — converts an ISO to a raw disk image
  • BUILD-ISO-STATUS.md, ISO-BUILD-CHECKLIST.md — contributor guides
  • branding/isohdpfx.bin — isolinux MBR hybrid image
  • .gitea-workflows/build-iso-dev.yml — CI workflow that ran the build+smoke-test

To resurrect

  1. git mv image-recipe/_archived/* image-recipe/ (adjust paths back)
  2. Restore .gitea/workflows/build-iso-dev.yml
  3. Re-add release-process references (see scripts/create-release.sh, docs/BETA-RELEASE-CHECKLIST.md, docs/hotfix-process.md, README.md).

Why archived

The release flow is simpler and faster as tarball-only:

  • releases/vX.Y.Z-alpha/archipelago (backend binary)
  • releases/vX.Y.Z-alpha/archipelago-frontend-X.Y.Z-alpha.tar.gz (frontend + AIUI + filebrowser UI assets)
  • releases/manifest.json (pointers + changelog)

Nodes pull these via scripts/self-update.sh from either Gitea mirror. Filebrowser and AIUI remain bundled inside the frontend tarball and deployed atomically by self-update.sh.