Repository navigation
Releases
Automagik Arca 0.31.0
A container service made from an OCI image keeps /run in memory (a tmpfs), never on the container's disk: a
short-lived secret staged there no longer touches the disk. Incus mounts a tmpfs on an OCI container's /run only
when the image keeps nothing there, so Arca now empties the image's /run on the root disk before the first start,
after each service_update rebuild, and in a service_reconfigure of a service made before (its card says
/run becomes memory, restart once), or in the one restart of a service_update with withTemplate, which carries
the same /run row. No project restriction is loosened and it works in tenants too. The mount has mode=755 but
neither nosuid nor nodev, and no size of its own: the service's memory limit bounds it when the template sets
limits.memory. Arca leaves /run on the disk, untouched, when an entry there is not root's (a non-root image's own
directory, which it needs) or cannot be read back by its name, and postgres-autopg says "runTmpfs": false, since
its image keeps its socket directory there. A template says "runTmpfs": false for any other image that needs its own
files in /run. The answers say run: "memory", or run: "disk" with the reason when /run was left on the disk,
in which case the service runs as before.
Arca can keep itself up to date. Every node looks for a newer release of automagik-si/arca every six hours (the new
update config key: on by default, releases only, at any hour; a window, the pre-release channel and the interval can
be set). It installs a release by itself only when the release's SHA256SUMS is signed by a key the program holds, and
no release signing key exists yet: until one is made, a node says which release is available (unsigned) and installs
nothing. The release workflow signs SHA256SUMS once the ARCA_RELEASE_SIGNING_KEY secret exists. A signed release is
installed with nobody at a terminal: the run finds every systemd unit that runs an Arca program (the installer's
arca.service, the guide's hand-made units, links, nodes with their own program path), checks the binary and the
release's install.sh against SHA256SUMS, replaces each program behind the release and keeps the old one as
<program>.previous, and restarts shims, then nodes, then links, one at a time. Each unit must come back within
update.healthSeconds, a node must answer on its own socket, and the unit must then stay up for update.healthSeconds
on the release's version. A unit that does not rolls every program back, fires the new kernel-update-failed alert,
and holds that release back until a newer one is published. A run cut off half-way is finished or rolled back by the
next one. A build from a branch is never replaced, and a node with an owner approval card waiting is not restarted until
none waits. The templates are brought up to the release as the installer does. arca_status shows the current and
available versions under update; arca update check says what a run would do, and arca update run is the run
itself. On Arca OS the program is in the read-only image, and the OS update brings it (os-managed); a program its user
may not write is staged in that user's state, and serve, shim and link serve hand over to it at their start.
- Merge feat/auto-update: arca updates itself from signed releases, with health watch, roll back and a one-fd hand-over
- Merge feat/janitor-hardening: no lazy fetch from a scanned partial clone, plus review 1 hardening
- Merge fix/service-run-tmpfs: /run in memory for services, kept across reconfigure, update withTemplate and rollback
arca-0.31.0-linux-x86_64 is one file for x86_64 Linux and arca-0.31.0-linux-aarch64 one for aarch64 (ARM) Linux. Each is built against glibc 2.34 and needs glibc 2.34 or newer. install.sh sets up a read-only node with this release: read it, then run sh install.sh. Check what you downloaded with sha256sum --check --ignore-missing SHA256SUMS, and stop unless it prints arca-0.31.0-linux-x86_64: OK or arca-0.31.0-linux-aarch64: OK, for the file you took.
Automagik Arca 0.30.0
instance_import moves one virtual machine from an outside hypervisor (the onevm show -x XML, passed in by
the operator) into Incus behind one owner card: the same CPUs, memory, firmware, disks and MACs, the source's
security groups as an Incus network ACL, a cloud-init seed from its context, a full sparse disk copy from the source
Ceph pool (read-only) into the Incus Ceph pool, and a read-back after the start. instance_import_undo stops and
removes an imported VM; the source is never written. A node needs kernel.instanceImport for either.
action_propose now reaches ghcr.io when a card shows Omni's API image (ghcr.io/automagik-si/omni-api): a
service_create, with or without digest, or a service_update of it. To name the build on the card's Version
row, the node asks anonymously over HTTPS for a pull token, the repository's tags (at most 5 pages) and the digests of
the newest 50 version tags. Nothing else is sent, no redirect is followed, and one round ends within 5 seconds. The
answer is kept as one map for at most ten minutes, so a node asks at most once a minute when unnamed digests are
proposed, and otherwise once every ten minutes. A node that cannot reach ghcr.io shows version unknown and refuses
nothing; a node with an egress allowlist that should name versions must allow ghcr.io:443, which Incus already uses
to pull the image.
One MCP door reaches the whole fleet: every read the door serves, and action_propose, take an optional node, the
name of one of approval.linkedHosts (arca_status lists them). The caller is checked on this kernel first, as for a
call of its own; the call then runs on that node with its linked token, and its answer comes back as the node gave it,
with linkedNode naming it (every field the node wrote is kept, so the answer fits the tool's own schema). A proposal made this way waits on that node, and this kernel's approval page shows it with the
machine named on the card. A name that is not linked is an invalid argument listing the linked names; a node that does
not answer is refused Unreachable, and one that refuses the token LinkToken. Without node nothing changes. The
linked kernel's token must admit the relayed verbs: the page's three-verb token does not. OPERATING.md ("Asking a linked
node") gives the one --tools line to mint it with; never mint it without --tools.
A node can make a token for the machine's own console: with console.tokenFile in the config, serve makes one viewer
token at each start, limited to node_metrics, arca_status, alerts_list and service_list, holds it in memory only
and writes it to that file at mode 0400. A reload keeps it, a restart replaces it, and a stop removes the file. The start
is refused when the file's directory is open to group or others or not the node user's, or when a link or another file is
at its path. token_list shows it as the console's (console: true, stored: false), arca status --security counts it
among the tokens that only look, and token revoke of it says to remove the key instead. A 403 to a tools/call with a stored
token now carries one line that names the refused verb; a GET route's 403 stays bare. See "The console's token" in docs/OPERATING.md.
arca.db no longer commits on every 5-second tick. The raw 5-second points stay in a ring in the server's memory for one
hour, and only their minute and hour rollups are written, one transaction a minute: 60 commits an hour where there were
780, which matters on consumer SSDs without power-loss protection, where every commit with synchronous=FULL is a real
flush. Alert events are still committed in the tick that makes them, with synchronous=FULL, and nothing else that is kept
changes. A crash or a power loss now loses at most the raw samples of the minute that had not closed; the raw window is
empty after a start until it fills again, and a read of it says so in words. A store from an earlier release has its raw
rows read into the ring at the first open and deleted from the file at the first rollup.
node_metrics and arca metrics --json say what the machine's compute and power are, as additions; no field a client
reads today changes. cpu.threads, cpu.physicalCores and cpu.busyThreads tell the logical CPUs, the physical cores
and how many threads were busy apart: cpu.cores keeps counting logical CPUs, so a 12-core, 24-thread machine still
says 24 there. A new power block gives each CPU package's power in watts from its powercap energy counter (a rate
between two samples, through the counter's wrap), their sum, each discrete GPU's own power (an NVIDIA card's
power.draw, or a discrete card's hwmon power1_input), and the whole-chip sensors in power.chip: on an APU, amdgpu's
PPT sensor holds the CPU and the integrated GPU, so it is never listed as a GPU. Arca tells the two apart by what the
driver shows beside the sensor (the vddnb voltage only on an APU; fan controls or pcie_bw only on a discrete card); a
sensor it cannot classify is never added. measuredPowerW holds each part once: the whole-chip sensors when they have a
figure, otherwise the CPU packages, and never both. notAdded names what was measured and left out because it overlaps,
and notIncluded what the sum does not hold: memory, disks, fans, the power supply's own loss, and any part without a
figure. It is not the power at the wall. A source without a figure says why in words: no counter on this machine, the counter is there
and this process may not read it (most kernels let only root read the package counters; the file is named), or only
one sample so far. A new instanceCpu block gives each running instance's CPU as threads in use since its previous
read, with its project and name: at most 50 rows, the largest first, and a count and a sum of the rest. An instance
that started, restarted or was replaced between two reads has no figure for that sample, never a negative or a huge
one. /metrics gains arca_node_cpu_threads, arca_node_cpu_physical_cores, arca_node_cpu_busy_threads,
arca_node_cpu_package_power_watts, arca_node_cpu_power_watts, arca_node_gpu_power_watts,
arca_node_chip_power_watts, arca_node_power_measured_watts and arca_instance_cpu_busy_threads.
A delete plan nobody approved within its fifteen minutes can be shown to the owner again without a restart: the new
operator verb plan_renew puts each lapsed plan back with fifteen new minutes and the same id, from what the journal still
holds, and says why for each one it leaves (a declined entry, an entry the desired state carries again, nothing left to
delete, or an earlier effect still unresolved). It sends nothing to Incus and writes no journal line. Until now a failed
create that had already made its data volume left that volume, and the network rule held for it, with no card to approve
once the plan lapsed.
The github-runner-pool controller builds one runner image on its machine before it begins any slot: the pinned
runner image with the Ubuntu packages of a new setting, aptPackages (by default libatomic1, build-essential,
zstd, wget, skopeo, xz-utils, zip, rsync and gh, which GitHub's ubuntu-latest has and the runner image lacks; settable at create), and
every runner starts from it. Without zstd no actions/cache saved with it restores; without libatomic1 pnpm cannot
start.
A build that fails is said in service_logs with the step and the package manager's last lines, no runner starts
without the image, and it is tried again after a minute, then less and less often (up to five minutes). An orderly
stop or restart of the controller inside the machine leaves a runner at its job to finish it, and the next controller
records it; a crash or an out-of-memory kill can lose the job. A pool that exists keeps the script and the settings it
was created with: it gets neither until it is created again.
The github-runner-pool template has a second registration mode for organisations that allow no App or token able to
register runners anywhere: registration set to registration-token, with runnerGroup naming the group. An owner's
one-hour registration token (the secret GITHUB_REGISTRATION_TOKEN) registers each slot once as a persistent runner;
each runner keeps its own registration in a root-only folder, the token is deleted once every slot is registered, and
the pool holds no GitHub credential. This mode keeps each slot's container, work directory and caches between jobs: a
bridge until each job has a machine of its own. The jit mode is unchanged.
service_update takes withTemplate: true: the same rebuild also makes the service what its current template says,
as service_reconfigure would (environment, links' values, secrets, ports, rawLxc, no-new-privileges, entrypoint),
behind one owner card and with one restart. The card shows the new digest and every setting that changes, secrets by
name only, and the approval binds both; an edit of the template after the proposal needs a new card. If the new
version does not come back healthy, Arca puts back the old image and the old record, its entrypoint among them: a
service that ran its image's own entrypoint runs it again. A reconcile now marks an entrypoint it writes
(user.arca.entrypoint) and takes off only a marked one. Without the flag an update is unchanged.
service_reconfigure makes a running container service what its current template says (environment values, the
secrets it declares, ports, links' values, rawLxc and noNewPrivileges) behind one owner card that shows the exact
difference key by key, secrets by name only; then it restarts the service once and reads its config back. Templates may
declare rawLxc lines (lxc.sched.core=0, say) that Arca keeps in raw.lxc beside lxc.no_new_privs=1 through every
reconcile; a service without them is reconciled as before. The create and reconfigure cards show raw.lxc whole, and
give every lin...
Automagik Arca 0.29.0
A function whose command is a shell and its script (["/bin/sh", "-c", <script>]) now starts on a node whose Incus
links liblxc 5.0 or older too: the script goes as the one word a service template's script goes as, so the image needs
base64. A function created earlier keeps the entrypoint it was made with: where it does not start, remove it and
create it again. A service template's script may again be about 32,700 bytes (it was about 24,500 since 0.27.0): the
entrypoint cap is now 43,760 bytes, measured on the base64 that is sent.
- Merge PR 165: a function's shell script goes as one word
arca-0.29.0-linux-x86_64 is one file for x86_64 Linux and arca-0.29.0-linux-aarch64 one for aarch64 (ARM) Linux. Each is built against glibc 2.34 and needs glibc 2.34 or newer. install.sh sets up a read-only node with this release: read it, then run sh install.sh. Check what you downloaded with sha256sum --check --ignore-missing SHA256SUMS, and stop unless it prints arca-0.29.0-linux-x86_64: OK or arca-0.29.0-linux-aarch64: OK, for the file you took.
Automagik Arca 0.28.0
Two new templates keep a cold copy of one node's NATS streams on a second node, over a private link between the two: nats-primary is the nats template with its leaf node port 7422 also offered on the node's link address (privatePort, so its create needs kernel.serviceListenAddresses and the owner's card), and nats-replica is a NATS of its own whose one leaf node remote dials that port, through kernel.serviceDestinations, with the address and the primary's leaf password as two secrets the owner sets. Each stream on the replica is a mirror of the primary's, made with the nats CLI, and OPERATING.md gives the set-up, how to read the mirrors' lag, the promotion when the primary is lost (it first cuts the replica's link, so an old primary that comes back cannot join it), and how to change the pair's password. The replica dials only the address the owner set, never one the primary tells it of. The nats template is unchanged. No pair has run on two nodes yet.
- Merge PR 162: nats-primary and nats-replica, a cold NATS replica on a second node over a private link
- Merge PR 161: README and quickstart name Incus 7.3 as what Postgres and NATS need
arca-0.28.0-linux-x86_64 is one file for x86_64 Linux and arca-0.28.0-linux-aarch64 one for aarch64 (ARM) Linux. Each is built against glibc 2.34 and needs glibc 2.34 or newer. install.sh sets up a read-only node with this release: read it, then run sh install.sh. Check what you downloaded with sha256sum --check --ignore-missing SHA256SUMS, and stop unless it prints arca-0.28.0-linux-x86_64: OK or arca-0.28.0-linux-aarch64: OK, for the file you took.
Automagik Arca 0.27.0
- A service template whose entrypoint runs a shell script (postgres-autopg) is created and starts on Incus 7.6, which
refuses a line break inoci.entrypoint, whichever liblxc that Incus links: Arca sends the script as one word with no
whitespace in it (its base64, with${IFS}for each space), which the container's own shell decodes and runs. This
needs Incus 7.3 or later. An entrypoint argument with a line break that is not such a script is refused before
anything is created. A service made earlier from a script entrypoint cannot start or be updated on Incus 7.6: remove
it and create it again.
A service template may set privatePort, which offers one port of the service on one host address that the node's config names (kernel.serviceListenAddresses), for a second node over a private link, and on no other address; the owner's create card names the address and the port. See OPERATING.md.
The nats template now writes its own configuration (every message fsynced, a JetStream domain, monitoring on 8222, and a leaf node listener on 7422 that only the user leaf may join, though no link reaches it yet) and pins NATS 2.14.10, which keeps the fsync promise that 2.10 does not for a block compaction; clients on 4222 still log in with nothing and NATS_URL is unchanged. A nats made before keeps its command line; service_update can move its image and keeps /data (a nats made up to 0.22.0 has none and is refused), but NATS documents no jump from 2.10 to 2.14 and its rollback puts 2.10 back over a store 2.14 may have rewritten, so a new service made from the template, which has the new settings, is the safe path (see "A message bus: nats" in docs/OPERATING.md).
- Merge PR 156: nats template v2 on NATS 2.14.10 by digest, every message fsynced, a JetStream domain, a leaf node listener and monitoring, and CI runs its script under the image's shell
- Merge PR 159: a service can listen on one private address of its node, named in the node config, for a peer node over a private link
- Merge PR 158: a script entrypoint reaches the container as one word with no whitespace, so it starts on every liblxc, and the fake models how Incus and liblxc split it
arca-0.27.0-linux-x86_64 is one file for x86_64 Linux and arca-0.27.0-linux-aarch64 one for aarch64 (ARM) Linux. Each is built against glibc 2.34 and needs glibc 2.34 or newer. install.sh sets up a read-only node with this release: read it, then run sh install.sh. Check what you downloaded with sha256sum --check --ignore-missing SHA256SUMS, and stop unless it prints arca-0.27.0-linux-x86_64: OK or arca-0.27.0-linux-aarch64: OK, for the file you took.
Automagik Arca 0.26.0
A service template may set noNewPrivileges: true, so a setuid or setcap binary inside the container cannot raise
privileges. It is off unless set, so every existing template and service is unchanged. It needs
restricted.containers.lowlevel=allow on the service project, a step on the node that Arca does not take; see
OPERATING.md. service_update gives an existing service the key, or takes it away, to match its template, with a
restart (which interrupts it) and a health check, and no rebuild, so its data stays where it is.
-
The guide names
admintokens besidedoctorandoperator, and says what puts the declared host network back
and what does not. -
Merge PR 155: the guide names admin tokens with doctor and operator, and says exactly what is and is not repaired by itself
-
Merge PR 154: a service template can run its container with no-new-privileges, gained or dropped on a running service by an update that restarts it and puts the old setting back if it fails
arca-0.26.0-linux-x86_64 is one file for x86_64 Linux and arca-0.26.0-linux-aarch64 one for aarch64 (ARM) Linux. Each is built against glibc 2.34 and needs glibc 2.34 or newer. install.sh sets up a read-only node with this release: read it, then run sh install.sh. Check what you downloaded with sha256sum --check --ignore-missing SHA256SUMS, and stop unless it prints arca-0.26.0-linux-x86_64: OK or arca-0.26.0-linux-aarch64: OK, for the file you took.
Automagik Arca 0.25.0
Arca now owns each host's forwarding and firewall as declared state, so a reboot or a Docker restart cannot take the
containers' way out again (Docker 29 turns IP forwarding on by itself and sets the FORWARD policy to DROP). The
owner's file /etc/arca/host.json says whether the host forwards and which bridges may reach out. A new root part of
the arca binary, arca host-network run, started by the system unit arca-host-network.service, sets the two
forwarding switches and puts one accept in and one for the answers out for each bridge into Docker's DOCKER-USER
chain, adding nothing twice. It does this when it starts: at boot after docker.service, and again on every Docker
start, since the unit is tied to Docker. Every minute it reads the host again and writes a status file (in sync, or
which item drifted), and it answers on a socket to two verbs only, read and apply-declared-state, neither with an
argument. The node raises the new critical alert host-network-drift for each item that drifts, and a new action,
host_network_restore, is a normal approval card: when the owner approves it, the node asks the socket to apply, and
the result is the read-back. arca host-network install --takeover <unit> writes the declared file from what the host
has now, copies the binary to a root-owned place, starts the unit and disables the hand-made unit named, so the hand fix
is replaced and not doubled; --dry-run prints every step. See "Host forwarding and the firewall" in docs/OPERATING.md.
Not done here: IPv6 firewall rules, and the canvas does not yet draw the new card (the owner's approval page does).
service_update no longer erases a service's data silently. It refuses, before it writes anything, a service whose
template declares a data volume but whose instance has none, which is how a database, a nats server or an Omni API made
before the volumes keep their data: the update would rebuild the root disk and the data with it. The refusal says so in
plain words and names the service and its template; it holds for a direct call, for action_propose and for an approved
proposal when it runs. To update such a service and start over with no data, eraseData: true is stated with the
digest, and it needs the owner's approval: service_update can now be proposed with action_propose, and the card says
that all the data is erased and cannot be brought back. A service that has its volume, and a service whose template
declares none, update exactly as before.
Two nodes joined by a private link, such as a fiber cable, can now use it for the link between them. The link config
section takes peers, a map from a peer's name to the ip:port addresses it is also reached on, and port, a fixed
UDP port so that address stays the same. While a named address works it carries the traffic ahead of the VPN, a LAN
address and the relay; when it does not, the link falls back to the normal path. Only the side that opens a connection
chooses its paths, so set port on both nodes and name each other in peers, or one direction may still use the VPN.
arca link peers now shows, while link serve runs, the path each peer is reached on from its open connections:
direct or relay with the address and whether the config named it, or idle when no connection is open. A taken
port stops link serve with a message that names the port. Without the two keys the link behaves as before; a
serving node also writes a small paths.json every 2 seconds. This turns on iroh's unstable-custom-transports
feature, which iroh 1.4.1 requires to prefer a path; iroh stays pinned to that exact version.
- Merge PR 152: a link prefers a named private path such as a fiber, falls back on its own, and arca link peers shows the path of each open connection
- Merge PR 150: service_update keeps a service's data, refuses an old-style service that would lose it, and erasing needs the owner
- chore(lock): arca-hostnet follows the workspace version, 0.24.0
- Merge PR 148: a node declares its host firewall and forwarding in /etc/arca/host.json, a root unit applies it, and drift raises an alert with a restore action
arca-0.25.0-linux-x86_64 is one file for x86_64 Linux and arca-0.25.0-linux-aarch64 one for aarch64 (ARM) Linux. Each is built against glibc 2.34 and needs glibc 2.34 or newer. install.sh sets up a read-only node with this release: read it, then run sh install.sh. Check what you downloaded with sha256sum --check --ignore-missing SHA256SUMS, and stop unless it prints arca-0.25.0-linux-x86_64: OK or arca-0.25.0-linux-aarch64: OK, for the file you took.
Automagik Arca 0.24.0
A new token scope, admin, sits above operator, and a node holds one admin token at a time: arca token mint --scope admin with another admin token on the node is refused naming it, and --replace retires the old one and has a running
node read its tokens at once. The admin token can approve a waiting action proposal from the terminal of an MCP client
that declared elicitation: the call stays open, the client is asked in the card's words, and an explicit accept with yes
approves and runs the proposal once. The journals record it as approved in the terminal by that admin token (the run is
made as terminal-approval:<token id>), never as the owner's. A decline, a cancel or a timeout leaves the proposal on
its card, and every other token and client is answered as before. See "Approving a plan from the terminal" in
OPERATING.md.
- Merge PR 102: Automagik's brand is copied into docs/brand from Automagik 00765fdb, and a brand copy cuts no release
- Merge PR 149: an admin token held by one terminal approves gated actions in that terminal through MCP elicitation; every other client keeps the web card
arca-0.24.0-linux-x86_64 is one file for x86_64 Linux and arca-0.24.0-linux-aarch64 one for aarch64 (ARM) Linux. Each is built against glibc 2.34 and needs glibc 2.34 or newer. install.sh sets up a read-only node with this release: read it, then run sh install.sh. Check what you downloaded with sha256sum --check --ignore-missing SHA256SUMS, and stop unless it prints arca-0.24.0-linux-x86_64: OK or arca-0.24.0-linux-aarch64: OK, for the file you took.
Automagik Arca 0.23.0
A node can now record a program that runs outside Incus, such as a macOS LaunchAgent next to the Incus VM, so it shows
in service_list, and on the machine's canvas of a node that runs services (a node that only looks shows it in
service_list alone). external_add takes a name, the kind host-program, an http or
https address and an optional health label; external_remove takes the record out. Both need a doctor token and run
at once, with no approval card, because they only write a line in the node's state (external.jsonl, which is also
its journal) and change nothing on the machine. The row says it is recorded and not managed by Arca; service_status
does one TCP connect to its address (3 seconds) and says up or down. Every verb that changes a service refuses it in
words that name external_remove.
A database (postgres-autopg), a nats server and an Omni API (omni-api) made from the shipped templates now keep
their data on a volume of their own: 20GiB for the database, 10GiB for nats and for Omni's media. service_update
rebuilds a service's root disk from the new image and keeps only its data volume, so data on the root disk would be
gone after an update. A service made before this release keeps its data on its root disk and gets no volume: the
changed templates are brought up to date by arca templates install, and apply to the services made from them
afterwards. Updating a service that has no data volume erases what it wrote to its root disk, and the docs now say so.
An action_propose answer now says where and by when: the approval page's address (approvalUrl), the time the card
expires, fifteen minutes after it was proposed, and how many owner passkeys the node itself trusts (passkeysTrusted).
While none is trusted, its nextStep says how to enrol one first, with the ssh -o ExitOnForwardFailure=yes -L line
when the page is on localhost only. A node set to trust another page host's passkeys (approval.trustOwnerKeysFrom or
approval.peerKeys) says instead that the card is approved on that host's page and needs no passkey on the node.
Before, the answer named none of this, so the person who asked for the action did not know where to approve it, nor
that it would lapse.
- Merge PR 137: an action_propose answer says where to approve the card and by when
- Merge PR 144: postgres-autopg, nats and omni-api keep their data on a volume of their own
- Merge PR 145: a node records a program that runs outside Incus, and status checks it by one TCP connect
arca-0.23.0-linux-x86_64 is one file for x86_64 Linux and arca-0.23.0-linux-aarch64 one for aarch64 (ARM) Linux. Each is built against glibc 2.34 and needs glibc 2.34 or newer. install.sh sets up a read-only node with this release: read it, then run sh install.sh. Check what you downloaded with sha256sum --check --ignore-missing SHA256SUMS, and stop unless it prints arca-0.23.0-linux-x86_64: OK or arca-0.23.0-linux-aarch64: OK, for the file you took.
Automagik Arca 0.22.0
Each release now also publishes arca-<version>-linux-aarch64, beside the x86_64 binary and in SHA256SUMS, built
on GitHub's arm64 runner with the same glibc 2.34 ceiling, so a Linux virtual machine on an ARM Mac can install and
upgrade from a release. install.sh picks the binary by uname -m: aarch64 and arm64 get the aarch64 one,
x86_64 the x86_64 one, and any other machine is refused in plain words, as before.
- Merge PR 143: Arca publishes a linux-aarch64 binary beside x86_64
arca-0.22.0-linux-x86_64 is one file for x86_64 Linux and arca-0.22.0-linux-aarch64 one for aarch64 (ARM) Linux. Each is built against glibc 2.34 and needs glibc 2.34 or newer. install.sh sets up a read-only node with this release: read it, then run sh install.sh. Check what you downloaded with sha256sum --check --ignore-missing SHA256SUMS, and stop unless it prints arca-0.22.0-linux-x86_64: OK or arca-0.22.0-linux-aarch64: OK, for the file you took.