Skip to content

docs(manual-tests): Record hull on Linux on a network gateway, 2026-11-18 - #674

Merged
ananos merged 1 commit into
mainfrom
docs/hull-linux-gateway-record
Nov 19, 2026
Merged

ananos merged 1 commit into
mainfrom
docs/hull-linux-gateway-record

Conversation

@ananos

@ananos ananos commented Nov 18, 2026

Copy link
Copy Markdown
Member

Summary

Brig puts a hull on Linux sandbox on a network gateway since #667, and refuses a policy, a divert and a published port there because no run on a real hull had shown they work. This is that run, on a fresh rootless install of brig-standalone-linux v0.1.0-rc22 (hull 4bf76a6, urunc 5c6bc70, hvi 0.1.0-rc.3, hull-assets 0.1.12) with Brig from main at cf80f90, on an amd64 host with KVM.

What holds: offline, isolated and shared postures; two isolated sandboxes cannot reach each other and a shared one cannot reach an isolated one; two shared ones can; brig rm --all -y leaves no gateway. At hull level, with the flags and API calls Brig uses on macOS: an egress policy is enforced (allowed hosts 200, denied hosts refused at DNS and logged), brig.internal and a link-local divert are answered by the host sockets, and /forwards publishes and withdraws a guest port.

What does not: hull refuses an image whose USER is a name, so the community images run only through their :root tags.

The page also records the three things that cost time in this run so the next one avoids them. A separate change flips the capability rows this evidence supports.

Related issues

Refs brig-sh/hull#105.

Changes

  • docs/manual-tests/hull-linux-gateway-2026-11-18.md: the record.

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)

…1-18

Brig puts a hull on Linux sandbox on a network gateway since #667, and
refuses a policy, a divert and a published port there because no run on
a real hull had shown they work. This records one, on a fresh rootless
install of brig-standalone-linux v0.1.0-rc22 with Brig from main: the
postures, sandbox-to-sandbox reachability, rm --all, and the three
refused capabilities driven at hull level with the flags and API calls
Brig uses on macOS. All hold. The one refusal is hull's own: an image
whose USER is a name.

Refs: brig-sh/hull#105
Signed-off-by: Anastassios Nanos <ananos@nofire.ai>
@ananos
ananos force-pushed the docs/hull-linux-gateway-record branch from f3a2ce3 to 73a3ed3 Compare November 18, 2026 18:09
@ananos
ananos marked this pull request as ready for review November 18, 2026 18:33
ananos added a commit that referenced this pull request Nov 19, 2026
The runtime now serves a divert, brig.internal and a published port on
hull on Linux, so the pages that said it refuses them were wrong. They
now put hull on Linux beside hvi: the same gateway, the same diverts and
the same API for forwards. The measured run is the record of 2026-11-18,
which #674 adds; that pull request merges first, since these pages link
its page.

Refs: brig-sh/hull#105
Signed-off-by: Anastassios Nanos <ananos@nofire.ai>
@ananos
ananos merged commit 6e94031 into main Nov 19, 2026
9 checks passed
@ananos
ananos deleted the docs/hull-linux-gateway-record branch November 19, 2026 08:37
ananos added a commit that referenced this pull request Nov 19, 2026
The runtime now serves a divert, brig.internal and a published port on
hull on Linux, so the pages that said it refuses them were wrong. They
now put hull on Linux beside hvi: the same gateway, the same diverts and
the same API for forwards. The measured run is the record of 2026-11-18,
which #674 adds; that pull request merges first, since these pages link
its page.

Refs: brig-sh/hull#105
Signed-off-by: Anastassios Nanos <ananos@nofire.ai>
ananos added a commit that referenced this pull request Nov 19, 2026
The runtime now serves a divert, brig.internal and a published port on
hull on Linux, so the pages that said it refuses them were wrong. They
now put hull on Linux beside hvi: the same gateway, the same diverts and
the same API for forwards. The measured run is the record of 2026-11-18,
which #674 adds; that pull request merges first, since these pages link
its page.

Refs: brig-sh/hull#105
Signed-off-by: Anastassios Nanos <ananos@nofire.ai>
ananos added a commit that referenced this pull request Nov 19, 2026
The runtime now serves a divert, brig.internal and a published port on
hull on Linux, so the pages that said it refuses them were wrong. They
now put hull on Linux beside hvi: the same gateway, the same diverts and
the same API for forwards. The measured run is the record of 2026-11-18,
which #674 adds; that pull request merges first, since these pages link
its page.

Refs: brig-sh/hull#105
Signed-off-by: Anastassios Nanos <ananos@nofire.ai>
ananos added a commit that referenced this pull request Nov 19, 2026
The runtime now serves a divert, brig.internal and a published port on
hull on Linux, so the pages that said it refuses them were wrong. They
now put hull on Linux beside hvi: the same gateway, the same diverts and
the same API for forwards. The measured run is the record of 2026-11-18,
which #674 adds; that pull request merges first, since these pages link
its page.

Refs: brig-sh/hull#105
Signed-off-by: Anastassios Nanos <ananos@nofire.ai>
ananos added a commit that referenced this pull request Nov 19, 2026
The runtime now serves a divert, brig.internal and a published port on
hull on Linux, so the pages that said it refuses them were wrong. They
now put hull on Linux beside hvi: the same gateway, the same diverts and
the same API for forwards. The measured run is the record of 2026-11-18,
which #674 adds; that pull request merges first, since these pages link
its page.

Refs: brig-sh/hull#105
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