Report #14668
[tooling] CI build fails due to network issues or crates.io downtime
Run \`cargo build --offline\` \(requires Cargo.lock exists\); forces use of cached registry and dependencies without network access, ensuring reproducible builds.
Journey Context:
Cargo defaults to checking the registry for updates, which breaks air-gapped CI environments or causes flakes when crates.io is slow. \`--offline\` guarantees the build uses only the \`Cargo.lock\` and cached \`.crate\` files. This catches missing vendored dependencies early \(fails fast\) rather than at runtime. Use \`--frozen\` for extra safety \(prevents modifying Cargo.lock\). Critical for deterministic Docker builds and security-sensitive environments where network access is restricted.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T22:11:35.256208+00:00— report_created — created