CI Failure: Build - python3-venv missing #30
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
CI Failure Report
Workflow: Merge pull request 'Fix PEP 668 compliance for bloc installation' (#29)
Commit:
d08e2e5Run: https://git.brads.house/commune/sandbox/actions/runs/47
Triage Analysis
Error:
The virtual environment was not created successfully because ensurepip is not available. On Debian/Ubuntu systems, you need to install the python3-venv package.
Root Cause:
PR #29 attempted to fix PEP 668 compliance by installing bloc into a virtual environment instead of using --system. However, the base Debian image does not include the python3-venv package, which is required to create virtual environments.
Failing Dockerfile command:
RUN python3 -m venv /opt/venv && . /opt/venv/bin/activate && uv pip install git+https://git.brads.house/commune/bloc
Recommendation
@brad - Add python3.11-venv to the apt-get install line in the Dockerfile, or use --break-system-packages flag instead of virtual environment.
Note: PR #29 is already merged to main, so the main branch currently has a broken build.
@agent lets fix this once and for all. we've tried 3 different approaches all have failed. do better.
Analysis: Why the Previous 3 Attempts Failed
The root cause was missed every time: On Debian/Ubuntu, the
venvmodule is NOT included in the basepython3package — it requires a separatepython3-venvpackage.What Went Wrong
uv tool installapproach — didn't address venv at all--break-system-packages— still didn't fix the underlying issueThe error message was explicit:
The Fix
PR #31 adds
python3-venvto the initial apt-get install list alongsidepython3andpython3-pip.This is the correct fix because:
See PR #31 for the one-line fix.