#20 - Add python3-venv to the base image #22

Merged

GuillaumeHemmen merged 1 commit from 20-add-python3-venv into master

2026-09-11 07:54:38 +00:00

claude-bot commented

2026-09-10 07:07:23 +00:00

Member

What

Add python3-venv to the base stage's package list, so every variant (ci, coder, coder-xfce-vnc) ships it.

Why

The image had python3 and python3-pip but not python3-venv. On Ubuntu that means no ensurepip, so python3 -m venv fails. Firebase Python deploys need it, and consuming CI jobs currently work around it with an in-job apt-get install -y python3-venv. Once this image is published, those jobs can drop that step.

Changes

Dockerfile: python3-venv added next to python3 / python3-pip, with a short comment explaining why.
README.md: Python 3 (pip, pipx, venv) added to the CI variant's feature list and to Version Information. Python wasn't mentioned anywhere before.

Verification

I pulled the base RUN step out of the Dockerfile with a script (continuations joined, comment lines dropped the way Docker does it) and ran it in an ubuntu:24.04 pod on the cluster:

Check	Result
Full base `RUN` step (apt list + Azul JDK)	pass
`python3-venv` installed	`3.12.3-0ubuntu2.1`
`python3 -m venv /tmp/v`	pass
`/tmp/v/bin/pip --version`	`pip 24.0 (python 3.12)`
`pip install six` into the venv, then import it	pass

The branch push also starts the docker-dev Kaniko build for all three targets.

Closes #20

🤖 Generated with Claude Code

https://claude.ai/code/session_01XPajGyTH2js52mY5WSJoNA

## What Add `python3-venv` to the **base** stage's package list, so every variant (`ci`, `coder`, `coder-xfce-vnc`) ships it. ## Why The image had `python3` and `python3-pip` but not `python3-venv`. On Ubuntu that means no `ensurepip`, so `python3 -m venv` fails. Firebase Python deploys need it, and consuming CI jobs currently work around it with an in-job `apt-get install -y python3-venv`. Once this image is published, those jobs can drop that step. ## Changes - `Dockerfile`: `python3-venv` added next to `python3` / `python3-pip`, with a short comment explaining why. - `README.md`: Python 3 (`pip`, `pipx`, `venv`) added to the CI variant's feature list and to Version Information. Python wasn't mentioned anywhere before. ## Verification I pulled the base `RUN` step out of the Dockerfile with a script (continuations joined, comment lines dropped the way Docker does it) and ran it in an `ubuntu:24.04` pod on the cluster: | Check | Result | |---|---| | Full base `RUN` step (apt list + Azul JDK) | pass | | `python3-venv` installed | `3.12.3-0ubuntu2.1` | | `python3 -m venv /tmp/v` | pass | | `/tmp/v/bin/pip --version` | `pip 24.0 (python 3.12)` | | `pip install six` into the venv, then import it | pass | The branch push also starts the `docker-dev` Kaniko build for all three targets. Closes #20 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01XPajGyTH2js52mY5WSJoNA

claude-bot added 1 commit

2026-09-10 07:07:23 +00:00

#20 - Add python3-venv to the base image

/ docker-dev-ci (push) Successful in 6m19s

Details

/ docker-dev-coder (push) Successful in 7m21s

Details

/ docker-dev-coder-xfce-vnc (push) Failing after 11m47s

Details

5cb0f2538e

The base stage shipped python3 and python3-pip but not python3-venv, so
`python3 -m venv` failed (no ensurepip). Firebase Python deploys and
consuming CI jobs worked around it with an in-job apt-get install.

Closes #20

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XPajGyTH2js52mY5WSJoNA