rossoctl / rossoctl/workload-harness
Runner image is OpenShift-incompatible (restricted-v2 SCC, venv write)
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 5
- Forks
- 6
- Avg merge
- 11h 37m
- Merged PRs (30d)
- 1
Description
Summary
In-cluster Job on OpenShift (OCP) fails because uv rewrites /app/.venv/ at startup (removes .gitignore, rebuilds venv). Under the restricted-v2 SCC, the random UID assigned by OCP cannot write there.
Setting HOME=/tmp UV_CACHE_DIR=/tmp/uv-cache gets past the cache-miss error but not the .venv mutation, so the Job still fails.
Workarounds / fix options
- Standard OCP Dockerfile hardening:
RUN chown -R 0:0 /app && chmod -R g+rwX /app - Invoke
exgentic-a2a-runnerviauv runfrom/app/.venv/bin/uv runsouvmanages the venv path.
Note: on kind the Job works perfectly — this is OCP-specific.
Found in
PR #33 review by @kellyaa.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the runner image Dockerfile and the exgentic-a2a-runner entry point, then reproduce the Job failure under OpenShift's restricted-v2 SCC rather than kind. Compare the two proposed fixes for /app/.venv write access and uv startup behavior; done means the Job starts successfully on OpenShift without relying on a writable image-owned venv.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100