[BUG] Offline image packaging cannot resolve boot-tool dependencies #172

Closed
opened 2026-10-20 23:16:39 +02:00 by erikinkinen · 3 comments
Owner

Summary

Offline image packaging stops while building boot-tool, after the selected services and EFI loader have compiled. The fixture creates a separate empty Cargo home, so it cannot resolve the tool's selected dependencies without network access.

Reproduction

Use Integration c8c8b54a59 and Bootloader 14f851ea072fb99c75f626667e50ba58fafe57c0. Prepare the selected component sources for offline compilation, then package the namespace-cancellation VM image with Rust 1.97.1. The fixture selects boot-tool 50e22cb05ac2e2fd460ea83ca9c0e80fb484af98 and starts its build in a new private Cargo home.

Expected and actual behavior

Packaging should build the selected boot-tool with its resolved offline dependencies and preserve the original source and lock. Instead, Cargo cannot check out the selected lib-bootimg dependency in offline mode and exits 101. No VM is launched.

Environment and identity

Linux x86-64 host; explicitly installed Rust 1.97.1; one Cargo job; offline Cargo. The revisions above identify the first observed failure. No last working revision has been established.

Evidence and prior checks

The original build completed 31 shared objects, the selected services and the EFI loader before the boot-tool lookup failed. Its complete output and original process results are retained. The existing BOOT_TOOL_CARGO_HOME setting forwards Git transport configuration; it does not supply the fixture's private Cargo home with the surrounding build's resolved dependencies.

Tracking

The fix spans Integration's image entry points and Bootloader's fixture script. The later extended VFS guest failure is tracked in #176. Related work: Integration PR #12.

  • Supply the selected boot-tool with its own offline Cargo inputs.
  • Check its original revision, tracked source and lock before and after compilation.
  • Cover cold builds, mismatched source and cancellation without changing caller timeout semantics.
  • Produce the image and run the original guest scenario.
## Summary Offline image packaging stops while building boot-tool, after the selected services and EFI loader have compiled. The fixture creates a separate empty Cargo home, so it cannot resolve the tool's selected dependencies without network access. ## Reproduction Use Integration c8c8b54a59716bb5831b14e3b6ba515aa76bb1b4 and Bootloader 14f851ea072fb99c75f626667e50ba58fafe57c0. Prepare the selected component sources for offline compilation, then package the namespace-cancellation VM image with Rust 1.97.1. The fixture selects boot-tool 50e22cb05ac2e2fd460ea83ca9c0e80fb484af98 and starts its build in a new private Cargo home. ## Expected and actual behavior Packaging should build the selected boot-tool with its resolved offline dependencies and preserve the original source and lock. Instead, Cargo cannot check out the selected lib-bootimg dependency in offline mode and exits 101. No VM is launched. ## Environment and identity Linux x86-64 host; explicitly installed Rust 1.97.1; one Cargo job; offline Cargo. The revisions above identify the first observed failure. No last working revision has been established. ## Evidence and prior checks The original build completed 31 shared objects, the selected services and the EFI loader before the boot-tool lookup failed. Its complete output and original process results are retained. The existing BOOT_TOOL_CARGO_HOME setting forwards Git transport configuration; it does not supply the fixture's private Cargo home with the surrounding build's resolved dependencies. ## Tracking The fix spans Integration's image entry points and Bootloader's fixture script. The later extended VFS guest failure is tracked in [#176](https://git.erikinkinen.fi/erix/integration/issues/176). Related work: [Integration PR #12](https://git.erikinkinen.fi/erix/integration/pulls/12). - [x] Supply the selected boot-tool with its own offline Cargo inputs. - [x] Check its original revision, tracked source and lock before and after compilation. - [x] Cover cold builds, mismatched source and cancellation without changing caller timeout semantics. - [x] Produce the image and run the original guest scenario.
Author
Owner

The next image build gets past the original dependency-lookup failure, but stops before boot-tool Cargo starts. The gateway places its work directory beside the nested boot-tool checkout, inside the Bootloader catalog source; the catalog correctly rejects that overlap.

I’ve reopened the offline-input criterion while correcting that placement. The kernel, services, image closure and EFI build completed, and the source trees and locks remained unchanged. No VM has started.

The next image build gets past the original dependency-lookup failure, but stops before boot-tool Cargo starts. The gateway places its work directory beside the nested boot-tool checkout, inside the Bootloader catalog source; the catalog correctly rejects that overlap. I’ve reopened the offline-input criterion while correcting that placement. The kernel, services, image closure and EFI build completed, and the source trees and locks remained unchanged. No VM has started.
Author
Owner

Published 8baabcb32f. The nested boot-tool factory now selects an explicit output parent beside the component checkouts. The gateway still rejects relative paths, links and storage inside selected sources.

All 27 focused checks pass, including the real nested source layout and the original overlap refusal. Source and documentation checks also pass. The original image build is next; the offline-input and guest criteria remain open until that production path succeeds.

Published 8baabcb32f54259cd8ebc3129289a8d798672de7. The nested boot-tool factory now selects an explicit output parent beside the component checkouts. The gateway still rejects relative paths, links and storage inside selected sources. All 27 focused checks pass, including the real nested source layout and the original overlap refusal. Source and documentation checks also pass. The original image build is next; the offline-input and guest criteria remain open until that production path succeeds.
Author
Owner

The original offline image producer now builds boot-tool 50e22cb0 with its selected private Cargo inputs, signs and verifies the image, and launches QEMU. The actual operation is outside every catalog source; the original source and lock checks remain intact. All four acceptance items are complete.

The guest emits its namespace-cancellation success marker and later exits 41 during extended VFS checks. That separate runtime failure is tracked in #176; the full VM scenario has not passed.

The original offline image producer now builds boot-tool 50e22cb0 with its selected private Cargo inputs, signs and verifies the image, and launches QEMU. The actual operation is outside every catalog source; the original source and lock checks remain intact. All four acceptance items are complete. The guest emits its namespace-cancellation success marker and later exits 41 during extended VFS checks. That separate runtime failure is tracked in [#176](https://git.erikinkinen.fi/erix/integration/issues/176); the full VM scenario has not passed.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34:20 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/integration#172
No description provided.