docs-tools¶
Documentation CI image: Zensical on Python 3.14. Derives from ci-base.
Release v0.1.6, 2026-11-04. Built on ci-base. Source: phpboyscout/images/docs-tools.
Pin it¶
Pin the full version. Each release also moves its minor tag and latest, which change under you.
| Variant | Tags |
|---|---|
| default | v0.1.6, v0.1 |
About this image¶
The documentation track's CI image.
Contains zensical on Python 3.14, on top of
ci-base.
One tool¶
infra-tools carried Zensical alongside seven others, so every repository
building a documentation site pulled tofu, tflint, trivy, gitleaks, checkov,
terraform-docs and the AWS CLI in order to run a static site generator.
No pipx¶
infra-tools installs Zensical through pipx. pipx exists to manage several
isolated applications for a user — it creates a venv per application and puts
shims on PATH. This image has exactly one application, so the venv pipx would
have created is the whole of what is needed, and python3 -m venv produces it
without the extra dependency.
Same reasoning that removed mise from
tofu-tools: a resolver
earns its place by resolving something.
pip is removed once the venv is built, and that is what makes zero
achievable: both findings the first build reported — an out-of-bounds read
in msgpack and a path traversal in setuptools — were pip's vendored copies.
Removing the apk package alone was not enough, because python3 -m venv
installs a second pip inside the venv, which is where the vendored copies
actually live.
Why the version lives in requirements-zensical.txt¶
The sibling images pin tools with annotated ARGs that Renovate's customManager
tracks. This one deliberately does not.
Renovate's pip_requirements manager already reads this file; it is where the
estate has kept this pin since the toolchain was baked into an image at all
(cicd spec 2026-07-13-bake-zensical-into-image); and pip resolves a
transitive tree, which a requirements file is the natural thing to describe.
Forcing the ARG pattern here would be consistency for its own sake.
The scan is split by who can fix it¶
| Job | Scope | Gate |
|---|---|---|
scan:os |
OS/apk packages — the base and anything we install | hard |
scan:tools |
Python distributions from PyPI | hard |
Both are hard here, kept as separate jobs so a failure says immediately which half is at fault.
tofu-tools makes its
scan:tools advisory because its findings are compiled into upstream Go
binaries and nothing it can do clears them. Python is not like that: pip
resolves the transitive tree at build time, so a fixed dependency is picked
up by the next rebuild — and the daily schedule means that happens without
anyone acting. A fixable finding here is therefore actionable.
This image measured zero findings when written, and the gate is what keeps that true.
Design record¶
Everything installed¶
Contents not yet published. This image's releases do not carry an SBOM yet. Until they do, the README above describes what it adds, and the Dockerfile is the full record.