Repository navigation
chore(ci): optimize Docker setup for ephemeral K8s pod runners - #348
Conversation
|
Note Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported. |
📝 WalkthroughWalkthroughModifies the Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
Comment |
0959ee7 to
2ed6427
Compare
2acffce to
0fc7edd
Compare
Signed-off-by: ppraneth <pranethparuchuri@gmail.com>
Description
Problem
The first
docker runon a fresh DinD pod is slow due to Docker daemon cold start. K8s pod runners pull Docker images (Oracle XE, Brave MCP) from Docker Hub on every CI run because pods are ephemeral and have no persistent image cache. Additionally, Docker container cleanup steps cause unnecessary delays since the pod is destroyed after job completion.Solution
21-slim-faststartfor faster DB startupChanges
Cleanup Brave MCP ServerandCleanup Oracle Databasestepsdocker infowarmup step (conditional onsetup_oracle || setup_brave)gvenzl/oracle-xe:21-slim→gvenzl/oracle-xe:21-slim-faststartTest Plan
Checklist
cargo +nightly fmtpassescargo clippy --all-targets --all-features -- -D warningspassesSummary by CodeRabbit
Release Notes