Skip to content

fix(install): Pin the Linux runtime bundle to v0.1.0-rc22 - #670

Merged
ananos merged 1 commit into
mainfrom
chore/runtime-rc22
Nov 19, 2026
Merged

ananos merged 1 commit into
mainfrom
chore/runtime-rc22

Conversation

@ananos

@ananos ananos commented Nov 18, 2026

Copy link
Copy Markdown
Member

Summary

install.sh pins brig-standalone-linux v0.1.0-rc21, whose urunc (3c00b69) ignores the netSocket, netAddress and netGateway annotations 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.env records all four:

URUNC_REF=5c6bc7060d4f6d33b0d4e8fd388f9f04cc88510b
HULL_REF=4bf76a6335d55016e5b29f27eb169730d4a28f20
HULL_PINNED=true
HVI_VERSION=0.1.0-rc.3
ASSETS_VERSION=0.1.12
ASSETS_URUNC_REF=5c6bc7060d4f6d33b0d4e8fd388f9f04cc88510b

The pin paragraph gains what rc22 brings. The signature identity and the floor (rc7) are unchanged. I have not run install.sh against 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 all passes (vet, test, build)
  • script/smoke.sh passes
  • I have added or updated tests covering the change
  • I have run go test ./... -race, if the change touches concurrency, subprocesses or the daemon
  • I have exercised the change against a real runtime (brig run <agent>), if it touches the run, exec or credential path
  • I have updated the affected docs (see docs/README.md for the map)

@ananos
ananos force-pushed the chore/runtime-rc22 branch from 0d41b9f to f301b60 Compare November 18, 2026 15:24
@ananos
ananos marked this pull request as ready for review November 18, 2026 15:24
@ananos
ananos force-pushed the chore/runtime-rc22 branch from f301b60 to 74bbf7e Compare November 18, 2026 17:00
@ananos ananos mentioned this pull request Nov 19, 2026
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
ananos force-pushed the chore/runtime-rc22 branch from 74bbf7e to e1834ec Compare November 19, 2026 08:38
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
ananos merged commit 5f89e1b into main Nov 19, 2026
9 checks passed
@ananos
ananos deleted the chore/runtime-rc22 branch November 19, 2026 09:25
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants