Skip to content

fix(docker): bump builder to rust:1.90 to satisfy dep MSRV #31

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
AndreaDiazCorreia merged 1 commit into from
May 15, 2026
Merged

fix(docker): bump builder to rust:1.90 to satisfy dep MSRV #31

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ For deeper context (data flow, components, ops): [docs/architecture.md](docs/arc

## Tech stack

- **Language**: Rust, edition 2021. MSRV 1.75 (Docker builder pinned to 1.83).
- **Language**: Rust, edition 2021. MSRV 1.75 (Docker builder pinned to 1.90).
- **Async runtime**: Tokio 1.35 (`full`).
- **HTTP**: `actix-web 4.9`, `actix-rt 2.9`.
- **Nostr**: `nostr-sdk 0.27`.
Expand Down
2 changes: 1 addition & 1 deletion Dockerfile
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
FROM rust:1.83 as builder
FROM rust:1.90 as builder

@chatgpt-codex-connector chatgpt-codex-connector Bot May 15, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Keep builder and runtime on same Debian release

On the Fly deploy path I checked (fly.toml builds this Dockerfile), rust:1.90 now resolves to the Trixie-based Rust image while the final stage remains debian:bookworm-slim. Because the release binary is dynamically linked against the builder's libc/OpenSSL stack and then copied into an older Bookworm runtime, deploys can build successfully but fail at container start with missing/newer symbol versions. Pin the builder to the matching suite, e.g. rust:1.90-bookworm, or move the runtime stage to Trixie as well.

Useful? React with 👍 / 👎.


WORKDIR /usr/src/app
COPY Cargo.toml Cargo.lock ./
Expand Down
Loading