image(broker): pin base to rust:1.96-slim so target install matches toolchain
ci / gates (push) Successful in 6s
ci / frontend (push) Successful in 25s
ci / publish (push) Failing after 54s
ci / rust (push) Failing after 2m12s
ci / e2e (push) Has been skipped

rust-toolchain.toml pins the workspace to 1.96.0. broker.Dockerfile used
rust:1-bookworm — some newer 1.x version — and `rustup target add` inside
that image installs the musl target under the container's default
toolchain. When cargo then reads rust-toolchain.toml and activates 1.96.0,
the target isn't there for that toolchain, so the build fails with
`E0463: can't find crate for core`. server.Dockerfile already uses
rust:1.96-slim; align broker to match.
This commit is contained in:
Omar Sobh
2026-07-05 16:08:34 -07:00
parent f351d0d495
commit bb3040c5db
+1 -1
View File
@@ -1,7 +1,7 @@
# The secret broker: its own minimal image, its own process boundary. # The secret broker: its own minimal image, its own process boundary.
# Shares the builder pattern with the server image; ships ONLY the broker # Shares the builder pattern with the server image; ships ONLY the broker
# binary. # binary.
FROM rust:1-bookworm AS builder FROM rust:1.96-slim AS builder
# git + cmake are needed for the clawhdf5 git dependency (fetched via the git # git + cmake are needed for the clawhdf5 git dependency (fetched via the git
# CLI — libgit2 chokes on Gitea smart-HTTP) and its zlib-ng C build (cmake). # CLI — libgit2 chokes on Gitea smart-HTTP) and its zlib-ng C build (cmake).
RUN case "$(uname -m)" in \ RUN case "$(uname -m)" in \