Repository navigation
fix(install): Pin the Linux runtime bundle to v0.1.0-rc22 - #670
Merged
Merged
Conversation
4 of 6 tasks
ananos
force-pushed
the
chore/runtime-rc22
branch
from
November 18, 2026 15:24
0d41b9f to
f301b60
Compare
ananos
marked this pull request as ready for review
November 18, 2026 15:24
ananos
force-pushed
the
chore/runtime-rc22
branch
from
November 18, 2026 17:00
f301b60 to
74bbf7e
Compare
3 of 6 tasks
rc22 carries hull built from a pinned commit (4bf76a6), urunc 5c6bc70, which reads the netSocket, netAddress and netGateway annotations hull sets for a network gateway, hull-assets 0.1.12, the kernel and initrd signed for that urunc, and hvi 0.1.0-rc.3. rc21's urunc, 3c00b69, ignores the annotations, so on an rc21 install hull refuses every networked run that joins a gateway and removes the instance. Refs: brig-sh/hull#105 Signed-off-by: Anastassios Nanos <ananos@nofire.ai>
ananos
force-pushed
the
chore/runtime-rc22
branch
from
November 19, 2026 08:38
74bbf7e to
e1834ec
Compare
ananos
added a commit
that referenced
this pull request
Nov 19, 2026
ci.yml runs script/smoke.sh against a stub runtime, so no CI run boots a VM. That hull on Linux works rested on one manual run on a lab host, and a change to internal/runtime or internal/wrap could break it with every check green. The new workflow runs on the self-hosted [self-hosted, Linux, X64, kvm] runner. The runtime bundle runs its containerd as a systemd --user unit, and the kvm-dind ARC pods have no systemd. It installs the bundle that install.sh pins, rootless, only when the runner's user lacks that version. It builds brig from the checkout and puts it behind the bundle's launcher, so the launcher runs the code under test. script/hull-linux-boot.sh holds one check per step: brig doctor, an offline boot on a kernel of its own, an isolated sandbox on a gateway of its own, a deny-by-default policy that refuses a name and an address, and brig rm leaving no sandbox, hull instance or gateway. Every name carries the run id, so cleanup removes this run's leftovers and nothing else. Pull requests from forks do not run on the host. The job fails on main today. install.sh pins v0.1.0-rc21, which ships no hull, so the setup step stops until #670 moves the pin to rc22. After that, the policy step fails until #675 lifts the refusal of a policy on hull on Linux. Refs: #670 Refs: #675 Signed-off-by: Anastassios Nanos <ananos@nofire.ai>
cmainas
approved these changes
Nov 19, 2026
ananos
added a commit
that referenced
this pull request
Nov 19, 2026
ci.yml runs script/smoke.sh against a stub runtime, so no CI run boots a VM. That hull on Linux works rested on one manual run on a lab host, and a change to internal/runtime or internal/wrap could break it with every check green. The new workflow runs on the self-hosted [self-hosted, Linux, X64, kvm] runner. The runtime bundle runs its containerd as a systemd --user unit, and the kvm-dind ARC pods have no systemd. It installs the bundle that install.sh pins, rootless, only when the runner's user lacks that version. It builds brig from the checkout and puts it behind the bundle's launcher, so the launcher runs the code under test. script/hull-linux-boot.sh holds one check per step: brig doctor, an offline boot on a kernel of its own, an isolated sandbox on a gateway of its own, a deny-by-default policy that refuses a name and an address, and brig rm leaving no sandbox, hull instance or gateway. Every name carries the run id, so cleanup removes this run's leftovers and nothing else. Pull requests from forks do not run on the host. The job fails on main today. install.sh pins v0.1.0-rc21, which ships no hull, so the setup step stops until #670 moves the pin to rc22. After that, the policy step fails until #675 lifts the refusal of a policy on hull on Linux. Refs: #670 Refs: #675 Signed-off-by: Anastassios Nanos <ananos@nofire.ai>
ananos
added a commit
that referenced
this pull request
Nov 20, 2026
ci.yml runs script/smoke.sh against a stub runtime, so no CI run boots a VM. That hull on Linux works rested on one manual run on a lab host, and a change to internal/runtime or internal/wrap could break it with every check green. The new workflow runs on the self-hosted [self-hosted, Linux, X64, kvm] runner. The runtime bundle runs its containerd as a systemd --user unit, and the kvm-dind ARC pods have no systemd. It installs the bundle that install.sh pins, rootless, only when the runner's user lacks that version. It builds brig from the checkout and puts it behind the bundle's launcher, so the launcher runs the code under test. script/hull-linux-boot.sh holds one check per step: brig doctor, an offline boot on a kernel of its own, an isolated sandbox on a gateway of its own, a deny-by-default policy that refuses a name and an address, and brig rm leaving no sandbox, hull instance or gateway. Every name carries the run id, so cleanup removes this run's leftovers and nothing else. Pull requests from forks do not run on the host. The job fails on main today. install.sh pins v0.1.0-rc21, which ships no hull, so the setup step stops until #670 moves the pin to rc22. After that, the policy step fails until #675 lifts the refusal of a policy on hull on Linux. Refs: #670 Refs: #675 Signed-off-by: Anastassios Nanos <ananos@nofire.ai>
ananos
added a commit
that referenced
this pull request
Nov 20, 2026
ci.yml runs script/smoke.sh against a stub runtime, so no CI run boots a VM. That hull on Linux works rested on one manual run on a lab host, and a change to internal/runtime or internal/wrap could break it with every check green. The new workflow runs on the self-hosted [self-hosted, Linux, X64, kvm] runner. The runtime bundle runs its containerd as a systemd --user unit, and the kvm-dind ARC pods have no systemd. It installs the bundle that install.sh pins, rootless, only when the runner's user lacks that version. It builds brig from the checkout and puts it behind the bundle's launcher, so the launcher runs the code under test. script/hull-linux-boot.sh holds one check per step: brig doctor, an offline boot on a kernel of its own, an isolated sandbox on a gateway of its own, a deny-by-default policy that refuses a name and an address, and brig rm leaving no sandbox, hull instance or gateway. Every name carries the run id, so cleanup removes this run's leftovers and nothing else. Pull requests from forks do not run on the host. The job fails on main today. install.sh pins v0.1.0-rc21, which ships no hull, so the setup step stops until #670 moves the pin to rc22. After that, the policy step fails until #675 lifts the refusal of a policy on hull on Linux. Refs: #670 Refs: #675 Signed-off-by: Anastassios Nanos <ananos@nofire.ai>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
install.shpins brig-standalone-linux v0.1.0-rc21, whose urunc (3c00b69) ignores thenetSocket,netAddressandnetGatewayannotations hull sets for a network gateway. With #667, every networked run on hull on Linux joins a gateway, so on an rc21 install hull refuses the run and removes the instance (asapranidis' finding on #667).rc22, released today from brig-standalone-linux main 4bb7c4e, carries hull built from a pinned commit (4bf76a6), urunc 5c6bc70, hull-assets 0.1.12 (the kernel and initrd signed for that urunc) and hvi 0.1.0-rc.3. Its
pins.envrecords all four:The pin paragraph gains what rc22 brings. The signature identity and the floor (rc7) are unchanged. I have not run
install.shagainst rc22 on a Linux host; the release's four bundles passed brig-standalone-linux's own CI (urunc, hull and hvi pins asserted, boot-asset digests checked).Related issues
Refs brig-sh/hull#105. Pairs with #667.
Changes
install.sh:RUNTIME_VERSION=v0.1.0-rc22, and the paragraph above it says what the pin carries.Checklist
make allpasses (vet, test, build)script/smoke.shpassesI have added or updated tests covering the changeI have rungo test ./... -race, if the change touches concurrency, subprocesses or the daemonbrig run <agent>), if it touches the run, exec or credential pathI have updated the affected docs (see docs/README.md for the map)