Conversation
📝 WalkthroughWalkthroughDockerfile now uses fedora:42 instead of python:3.13, switching provisioning from apt to dnf. It installs Python 3.13 (and pip) and various utilities via dnf, updates cleanup commands, and retains grpcurl install. Minor formatting changes; remaining build steps and behavior stay the same. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes ✨ Finishing Touches🧪 Generate unit tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR/Issue comments)Type Other keywords and placeholders
Status, Documentation and Community
|
|
The following are automatically added/executed:
Available user actions:
Supported labels{'/wip', '/hold', '/verified', '/lgtm', '/cherry-pick', '/build-push-pr-image'} |
|
/build-push-pr-image |
|
Status of building tag pr-521: success. |
|
/build-push-pr-image |
|
Status of building tag pr-521: success. |
There was a problem hiding this comment.
Actionable comments posted: 3
🧹 Nitpick comments (2)
Dockerfile (2)
1-1: Prefer Fedora’s canonical registry imageFor supply chain clarity and fresher metadata, consider pulling Fedora images from registry.fedoraproject.org.
-FROM fedora:42 +FROM registry.fedoraproject.org/fedora:42
6-6: Align UV_PYTHON with Fedora packagingIf Fedora 42’s default python3 is already 3.13, you can avoid version-specific package names and point uv to python3. This prevents breakage when Fedora revs Python.
-ENV UV_PYTHON=python3.13 +ENV UV_PYTHON=/usr/bin/python3And ensure dnf installs python3 and python3-pip (see earlier comment).
Also applies to: 14-16
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
Dockerfile(2 hunks)
🔇 Additional comments (1)
Dockerfile (1)
25-26: Sanity-check uv inside the Docker image
The host-side check didn’t validate the image itself (sinceuvisn’t installed on your machine). Please verify in the built container:• Build the image:
docker build -t uv-test .• Confirm uv, Python, and PATH:
docker run --rm uv-test uv --version \ && python3 --version \ && which uv• Test the sync step and entrypoint:
docker run --rm uv-test uv run --versionIf
UV_NO_SYNC=1is blocking the sync, either unset it for that step:RUN UV_NO_SYNC=0 uv syncor remove the
ENV UV_NO_SYNC=1line if it isn’t needed.
|
Status of building tag latest: success. |
(cherry picked from commit 69dc0d3)
Description
How Has This Been Tested?
Merge criteria:
Summary by CodeRabbit