ci: switch to ubuntu-slim where possible
#164
Conversation
📝 WalkthroughSummary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings. WalkthroughThree GitHub Actions workflow files have their runner image changed from Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Pre-merge checks and finishing touches❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
📜 Review details
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
📒 Files selected for processing (3)
.github/workflows/build.yml.github/workflows/cleanup.yml.github/workflows/release.yml
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)
- GitHub Check: build / image (debian-13)
- GitHub Check: build / image (fedora-43)
- GitHub Check: build / image (fedora-42)
- GitHub Check: build / image (archlinux)
🔇 Additional comments (3)
.github/workflows/build.yml (2)
18-18: LGTM: Appropriate migration of lightweight setup job.The ubuntu-slim runner executes workflows inside a container rather than a full VM instance, making it ideal for this lightweight setup job that only needs
find,jq, and basic file system operations.The job has
timeout-minutes: 5which is well within the 15-minute execution limit for ubuntu-slim.
31-31: LGTM: Correctly keeping the image job on ubuntu-24.04.This job appropriately remains on
ubuntu-24.04because it requires Docker (docker/build-push-action), Podman, and X11/Xvfb for testing—none of which are available in the container-based ubuntu-slim runner environment.This demonstrates the correct interpretation of the PR title "switch to ubuntu-slim where possible" by migrating only the jobs that can run in a minimal container environment.
.github/workflows/cleanup.yml (1)
18-18: LGTM: Appropriate migration of lightweight setup job.The ubuntu-slim runner executes workflows inside a container, which is ideal for this setup job that performs lightweight operations (file discovery, git refs, GitHub API calls).
The job has
timeout-minutes: 5which is well within the 15-minute execution limit for ubuntu-slim.
| runs-on: ubuntu-slim | ||
| timeout-minutes: 15 |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
find .github/workflows -name "cleanup.yml" -type fRepository: ddterm/gnome-shell-image
Length of output: 97
🌐 Web query:
ubuntu-slim GitHub Actions runner 15 minute limit
💡 Result:
Yes — the GitHub-hosted ubuntu-slim runner is a 1 vCPU / 5 GB RAM lightweight runner and jobs on it are limited to 15 minutes; jobs that hit the 15‑minute limit are terminated and fail. [1][2]
Sources:
- GitHub Docs — GitHub-hosted runners (ubuntu-slim: 1 vCPU, 5 GB; job timeout 15 minutes). [1]
- GitHub Changelog — 1 vCPU Linux runner (public preview) notes 15‑minute execution limit. [2]
🏁 Script executed:
cat .github/workflows/cleanup.yml | head -100Repository: ddterm/gnome-shell-image
Length of output: 2330
Adjust timeout to provide safety margin for ubuntu-slim runner's 15-minute hard limit.
The ubuntu-slim runner enforces a strict 15-minute job limit; jobs exceeding this are terminated and fail. This job's timeout-minutes: 15 (line 51) exactly matches this hard limit, leaving no margin for execution time variance.
The job runs container-registry-prune-action across 7 images in a matrix, performing network-dependent registry operations. These operations can have variable latency. If any run approaches or slightly exceeds 15 minutes, it will fail.
Increase timeout-minutes to 20 or higher, or verify through recent GitHub Actions run history that all recent completions finish consistently within 10–12 minutes.
🤖 Prompt for AI Agents
.github/workflows/cleanup.yml lines 50-51: the job timeout is set to 15 minutes
which matches the ubuntu-slim runner hard limit and leaves no safety margin;
update timeout-minutes to a higher value (e.g., 20) to provide buffer for
variable network latency, or alternatively validate recent run durations and set
timeout-minutes to a value that comfortably exceeds the observed max (e.g.,
12–20 minutes) before committing.
There was a problem hiding this comment.
This job always finishes in less than 15 minutes (unless there's a ghcr.io outage that causes timeouts). Actually, it takes less than 1 minute usually. So I do not see a problem here.
There was a problem hiding this comment.
@amezin, thank you for clarifying! Given that the job typically completes in under a minute and your operational experience shows it consistently stays well within the 15-minute limit, the current timeout configuration is appropriate. I appreciate the context about the actual runtime behavior.
| jobs: | ||
| release: | ||
| runs-on: ubuntu-24.04 | ||
| runs-on: ubuntu-slim |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
cat -n .github/workflows/release.ymlRepository: ddterm/gnome-shell-image
Length of output: 2826
🌐 Web query:
GitHub Actions ubuntu-slim runner available tools gh jq date
💡 Result:
Short answer:
- date: available (part of coreutils). [1]
- gh (GitHub CLI): NOT guaranteed on ubuntu-slim — not listed in docs; install it in your job if you need it. [1][2]
- jq: NOT guaranteed on ubuntu-slim — install it in your job if required. [1][2]
Why / sources:
- GitHub docs state ubuntu-slim is a minimal single-CPU container with a "minimal set of tools" and point to the actions/runner-images README for included software; there is currently no published full list for ubuntu-slim (issue tracking this request). [1][2]
How to check or install in a job (example steps):
- Check at runtime: run: gh --version || echo "gh missing"; jq --version || echo "jq missing"; date.
- Install if missing:
- GitHub CLI: run: sudo apt-get update && sudo apt-get install -y gh (or use actions/setup-gh).
- jq: run: sudo apt-get update && sudo apt-get install -y jq.
Sources:
[1] GitHub-hosted runners reference (ubuntu-slim is a minimal single-CPU container).
[2] actions/runner-images issue requesting a published list of software on ubuntu-slim (no full list available).
Add installation steps for gh and jq or revert to ubuntu-latest.
This job will fail on ubuntu-slim because GitHub CLI (gh) and jq are not included in the minimal ubuntu-slim runner. The workflow depends on these tools in multiple steps:
gh api(existing-tags step)jq(version parsing in existing-tags and version steps)gh release list,gh release create,gh workflow run(subsequent steps)
Either add installation steps before these tools are used:
- run: sudo apt-get update && sudo apt-get install -y gh jqOr revert the runner to ubuntu-latest where these tools are pre-installed.
🤖 Prompt for AI Agents
.github/workflows/release.yml around line 18: the job uses the ubuntu-slim
runner but later steps call tools not present on that minimal image (gh and jq),
causing the workflow to fail; either change the runner back to ubuntu-latest or
add installation steps before any use of gh/jq — e.g., run apt-get update and
install gh and jq (or use the official gh install) so gh api, gh release, gh
workflow run and jq invocations succeed; ensure the install runs in the same job
before the steps that call gh/jq.
There was a problem hiding this comment.
Somehow it succeeded just now. So apparently gh and jq are actually preinstalled in ubuntu-slim?
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
GitHub Actions ubuntu-slim runner preinstalled tools 2025
💡 Result:
Short answer: GitHub's ubuntu-slim runner is a single‑CPU, container-based, public‑preview runner with a minimal set of preinstalled tools (intended for short/lightweight jobs). GitHub has not published a full, separate "ubuntu-slim" software bill‑of‑materials like it does for ubuntu-latest; the exact tools on the container used for a given run are exposed via the workflow log "Included Software" link for that run. See GitHub docs and related repo/issue notes. [1][2][3]
Sources:
- GitHub Actions docs — github-hosted runners (ubuntu-slim description, runtime limits, and note that a minimal toolset is provided; workflow logs include an "Included Software" link). [1]
- actions/runner-images issue requesting an ubuntu-slim included‑software list (no formal list published as of the discussion). [2]
- Community tools/notes mentioning absence of an official ubuntu-slim list and how migration tools currently infer availability. [3]
If you want, I can: (a) run an example workflow to capture the exact "Included Software" link for a specific ubuntu-slim run, or (b) try to assemble a best-effort list of commonly available commands by inspecting recent runner logs/releases. Which do you prefer?
🏁 Script executed:
#!/bin/bash
# Check recent workflow runs for this PR to see the results
gh pr view 164 --json url,statusCheckRollup --jq '.statusCheckRollup[] | select(.workflowName == "release") | {name: .name, conclusion: .conclusion, targetUrl: .targetUrl}'
Length of output: 0
🏁 Script executed:
#!/bin/bash
# Try to get more info about recent workflow runs
gh run list --repo ddterm/gnome-shell-image --limit 10 --json workflowName,conclusion,createdAt,event,headBranch | jq '.[] | select(.headBranch == "ubuntu-slim")'
Length of output: 609
@amezin You're absolutely right, and I apologize for the incorrect warning!
Looking at the workflow runs, I can see the push workflow on the ubuntu-slim branch completed successfully, which confirms that gh and jq are indeed available on the ubuntu-slim runner.
While GitHub hasn't published an official comprehensive list of preinstalled tools for ubuntu-slim (unlike ubuntu-latest), it appears that common utilities like the GitHub CLI (gh) and jq are included in the minimal toolset. Your successful run is the best evidence of what's actually available.
Thank you for testing this and correcting my analysis. The change to ubuntu-slim should work fine for this workflow.
No description provided.