archipelagoandClaude Opus 5
8e814ca06a
Demo images / Build & push demo images (push) Failing after 2m22s
Replaces the registry host across 86 files: 309 references, covering all 40 app manifests, the orchestrator and container crates, the release and catalog scripts, both demo-images workflows, the ISO builder, demo-deploy, and the frontend marketplace data. Verified the domain actually serves the registry before rewriting anything, rather than assuming the web host implies the registry: - TLS verifies clean, HTTP/2 on the web root - an anonymous token grants a manifest fetch (HTTP 200) with no credentials - skopeo inspect --no-creds resolves an image and lists its tags That last check is the one that matters: an outside developer with no account can now pull, which was the functional blocker for publishing at all. Plain-HTTP references become HTTPS in the same pass, so OTA downloads stop crossing the network in the clear. Deliberately NOT rewritten: - The public FIPS anchor on port 8444. It is a functional network endpoint every node dials to bootstrap the mesh — closer to Bitcoin Core's hardcoded seeds than to leaked infrastructure. The domain does resolve to the same host, so it could become a hostname, but that adds a DNS dependency to the path used precisely when things are broken. Worth a deliberate decision, not a side effect of this change. - The companion APK on port 2100. The domain returns 404 for that path, so rewriting it would swap a working URL for a broken one. The Releases page does serve (200), which is where the plan already wants those binaries. - releases/app-catalog.json, releases/manifest.json and release-manifest.json. These carry `signature` and `signed_by`; editing their contents invalidates the signature and the fleet refuses artifacts that fail verification. They were rewritten in a first pass and reverted — they must be regenerated and re-signed through the signing ceremony instead, which needs the mnemonic. So the catalog still advertises the old host until that ceremony runs. Nodes resolve images through the signed catalog, not the on-disk manifests, so this commit alone does not change what a node pulls. Verified: archipelago-container 75/75; every manifest still parses with a top-level app block; no signed artifact modified. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
79 lines
2.7 KiB
YAML
79 lines
2.7 KiB
YAML
app:
|
|
id: barkd
|
|
name: Ark Wallet
|
|
version: 0.3.0
|
|
description: Ark protocol wallet daemon (barkd). Lets the node hold self-custodial off-chain bitcoin via an Ark server; the wallet talks to it over a local REST API. Signet by default while Ark matures.
|
|
|
|
container:
|
|
# barkd packaged from the pinned upstream release binary (no usable
|
|
# upstream image exists — their registry is empty). Built from
|
|
# apps/barkd/Dockerfile and pushed to the node registry. Pin the tag to
|
|
# match the REST shapes coded in core/archipelago/src/wallet/ark_client.rs
|
|
# (validated against barkd 0.3.0 on signet, 2026-07-14).
|
|
image: source.archipelago-foundation.org/lfg2025/barkd:0.3.0
|
|
pull_policy: if-not-present
|
|
network: archy-net
|
|
# The entrypoint installs the shared secret below via `barkd secret
|
|
# refresh` (so the wallet bridge can derive the matching Bearer token) and
|
|
# execs the daemon. The Ark wallet itself is created over REST by the
|
|
# bridge on first use (wallet.ark-* RPCs) with the node's ark_config
|
|
# (default: Second's public signet server) — no host provisioning needed.
|
|
generated_secrets:
|
|
- name: barkd-secret
|
|
kind: hex32
|
|
secret_env:
|
|
- key: BARKD_SECRET
|
|
secret_file: barkd-secret
|
|
data_uid: "1000:1000"
|
|
|
|
dependencies:
|
|
- storage: 1Gi
|
|
|
|
resources:
|
|
# barkd is a single wallet daemon (SQLite + a gRPC conn to the Ark server
|
|
# + esplora polling); steady state is tiny. Cap it so a stuck sync can't
|
|
# starve the node.
|
|
cpu_limit: 1
|
|
memory_limit: 512Mi
|
|
disk_limit: 1Gi
|
|
|
|
security:
|
|
readonly_root: true
|
|
# Needs outbound HTTPS to the Ark server (ark.signet.2nd.dev) and the
|
|
# esplora chain source, plus the published REST port for the wallet
|
|
# bridge. No inbound requirements beyond that.
|
|
network_policy: bridge
|
|
|
|
ports:
|
|
# barkd REST bound to 3535 in-container (BARKD_BIND_PORT); 3535 is free on
|
|
# the host (see port_allocator.rs). The Rust bridge targets
|
|
# http://127.0.0.1:3535.
|
|
- host: 3535
|
|
container: 3535
|
|
protocol: tcp
|
|
bind: 127.0.0.1
|
|
auth: local
|
|
|
|
volumes:
|
|
# Holds the wallet DB, mnemonic and auth token. ARK funds are recoverable
|
|
# on-chain from this datadir (unilateral exit) — include it in backups.
|
|
- type: bind
|
|
source: /var/lib/archipelago/barkd
|
|
target: /data
|
|
options: [rw]
|
|
|
|
environment:
|
|
- BARKD_DATADIR=/data
|
|
- BARKD_BIND_HOST=0.0.0.0
|
|
- BARKD_BIND_PORT=3535
|
|
|
|
# All /api/v1/* routes require the Bearer token, so an HTTP probe would 401
|
|
# forever — use a TCP probe like fmcd (the host-side lifecycle layer
|
|
# verifies reachability).
|
|
health_check:
|
|
type: tcp
|
|
endpoint: localhost:3535
|
|
interval: 30s
|
|
timeout: 5s
|
|
retries: 3
|