archipelago 9e6c5370fc feat(immich): manifest-driven stack via orchestrator — live-migrated on .228
Completes the immich migration off the legacy hardcoded install_immich_stack
(podman run + sudo chown) to the registry-manifest + orchestrator path. Validated
live on .228 (clean single set, healthy v2.7.4, data dir ownership correct).

- install_immich_stack now tries install_stack_via_orchestrator(immich_stack_app_ids)
  first; legacy remains only as the no-manifests fallback.
- immich-{postgres,redis,server} manifests corrected from live findings:
  * named by app_id (dropped container_name override) — using container_name
    spawned DUPLICATE containers (app_id-named install vs name-override reconcile)
    on the same PGDATA, which corrupted a postgres cluster. Server reaches its
    siblings via app_id aliases (DB_HOSTNAME=immich-postgres, REDIS=immich-redis).
  * immich-postgres data_uid 100998:100998 (postgres drops to container 999 →
    host 100998 under rootless; verified the fresh dir is chowned correctly).
  * immich-server version "release"→"2.7.4" (manifest validation requires a digit;
    the bad version made the manifest silently skip → partial orchestrator install
    → legacy fallback → the duplicate corruption above).
- HARDEN install_stack_via_orchestrator: only fall back to the legacy installer
  when NOTHING was installed yet. An "unknown app_id" AFTER a member is up now
  errors instead of double-creating containers on shared data (the corruption
  root cause).
- Strict the all-manifests round-trip test: fail (not skip) on any invalid shipped
  manifest — this gap let the bad immich-server version through.

Known follow-up (pre-existing, platform-wide): orchestrator-installed backends
(immich, btcpay-db) run as podman --restart, not Quadlet, and podman-restart.service
is disabled on .228 → reboot-survival gap independent of this migration.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-21 07:08:45 -04:00
..
2026-01-24 23:18:24 +00:00
2026-06-12 03:00:15 -04:00
2026-06-12 03:00:15 -04:00

Archipelago App Manifests

Containerized applications for the Archipelago Bitcoin Node OS. All apps run in rootless Podman with security hardening (cap-drop ALL, readonly root, non-root user, memory limits).

App Categories

Bitcoin & Lightning

  • bitcoin-knots — Full Bitcoin node (v28.1)
  • lnd — Lightning Network Daemon (v0.17.4-beta)
  • btcpay-server — Payment processor (v1.13.5)
  • mempool — Block explorer and fee estimator (v2.5.0)
  • electrumx — Electrum server
  • fedimint — Federated Bitcoin minting (v0.10.0)

Nostr

  • nostr-rs-relay — High-performance Rust relay (v0.9.0)
  • nostrudel — Nostr web client (v0.40.0)

Web5 & Identity

  • did-wallet — Web5 DID Wallet

Self-Hosted Services

  • nextcloud (v28), jellyfin (v10.8.13), immich (release), photoprism (v240915)
  • vaultwarden (v1.30.0-alpine), penpot (v2.4)
  • homeassistant (v2024.1), filebrowser (v2.27.0), searxng (2024.11.17)
  • ollama (v0.5.4), grafana (v10.2.0), portainer (v2.19.4)

Networking

  • tailscale (stable), nginx-proxy-manager (v2.12.1)

Custom & External

  • indeedhub — Bitcoin documentary streaming (custom build)
  • router — Mesh routing and network management
  • botfights, nwnn, 484-kitchen, call-the-operator, arch-presentation, syntropy-institute, t-zero — External web apps

Manifest Format

Each app has a manifest.yml defining container image, resources, dependencies, security policies, health checks, and network config. See docs/app-manifest-spec.md for the spec.

Quick Reference