You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Release blocker: the image bundles GPL/LGPL code; move it to scratch with static binaries #77
What: The shipped image is built on a base that bundles GPL or LGPL code: Dockerfile (python:3.12-slim). Move it to scratch (or an equally clean static base) with static binaries. Why: Steve, 2026-11-15: "don't bundle anything gpl, including lgpl", and the rule covers container images: every image moves to scratch or a static base with static binaries, and an image that cannot blocks the release. How:python:3.12-slim is Debian: glibc (LGPL), bash, coreutils and dpkg (GPL), and readline (GPL) linked by CPython's readline module. Options, in order: (1) a static CPython built against musl without GPL modules (no readline, no gdbm), copied with the venv onto scratch; (2) a shared runtime image that every Python repo uses, built once that way. Check every wheel's native libraries (auditwheel show) for GPL/LGPL code. The shared base is tracked once, at agent-runtime; the other Python repos follow it.
Done when: the final image's file list (crane export or the layer tarballs) holds no GPL, LGPL or AGPL file. Every file is either ours (MIT) or listed in THIRD_PARTY_LICENSES under a permissive licence. The image still passes its tests, and the release notes name the new base.
Activity