pin to trixie

[d4mr]

Summary by CodeRabbit

• Chores
  • Upgraded the application’s container base OS to a newer Debian release, modernizing both build and runtime environments.
  • Provides fresher security patches, updated system libraries, and improved compatibility with current toolchains.
  • No feature or behavior changes expected; existing workflows should continue to work.
  • If you rely on OS-level binaries within the container, verify versions in your environment.

[coderabbitai]

Walkthrough

Updated Docker base images in server/Dockerfile: cargo-chef helper image from latest-rust-1 to latest-rust-1-trixie, and runtime image from debian:bookworm-slim to debian:trixie-slim. No build steps or commands changed.

Changes

Cohort / File(s)	Change summary
Docker base image updates server/Dockerfile	Switched cargo-chef stage tag to latest-rust-1-trixie and runtime base to debian:trixie-slim; build/run steps unchanged.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title Check	❓ Inconclusive	The title “pin to trixie” references the base image update to Debian Trixie but is too generic to clearly convey that the Dockerfile’s base images are being pinned to trixie-slim.	Consider specifying what is being pinned and where, for example “Update Dockerfile to pin base images to Debian trixie-slim.”

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch pb/update-dockerfile

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 3774a4b and 4a389af.

📒 Files selected for processing (1)

• server/Dockerfile (2 hunks)

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

Confirm cargo-chef trixie tag exists.

I’m not seeing documentation for lukemathwalker/cargo-chef:latest-rust-1-trixie; please verify the tag actually exists, otherwise the build will fail when the base image can’t be pulled.

Run this to confirm the tag is published:

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

image="lukemathwalker/cargo-chef"
tag="latest-rust-1-trixie"

curl -s "https://hub.docker.com/v2/repositories/${image}/tags/?page_size=100" |
  jq -e --arg tag "$tag" '.results[] | select(.name == $tag)' >/dev/null ||
  { echo "Tag $tag not found for $image"; exit 1; }

echo "Tag $tag is available for $image"

Length of output: 64

---

Use a valid cargo-chef base image tag
The tag latest-rust-1-trixie does not exist on Docker Hub. Update line 2 in server/Dockerfile to reference a published tag for lukemathwalker/cargo-chef.

🤖 Prompt for AI Agents

server/Dockerfile lines 2-2: the FROM line uses a non-existent tag
`latest-rust-1-trixie`; update that line to reference a published
lukemathwalker/cargo-chef tag available on Docker Hub (e.g., pick the current
stable release tag or `latest` if present), then verify the chosen tag exists on
Docker Hub and rebuild to confirm the base image resolves.