← ClaudeAtlas

python-container-imagelisted

Use when a Python program that ships as a container image gets its image build or changes it — a Dockerfile and its ignore file, the base image, how dependencies get in, the user the process runs as, or how the platform's stop signal reaches the process. Owns a runtime image carrying only the installed program, an install of exactly what the lock file pins that fails where the lock has drifted, one interpreter across build and runtime, a non-root user named by number, no secret in any layer, a build context that admits only what the build reads, one image per runnable distribution and for every environment, unbuffered output, a server reachable from outside the container, and a stop signal the process acts on. Holds for a service of either architecture family and for a CLI tool shipped as an image; a library, and a CLI tool distributed as a package, have no image. Several members and their compose file are `python-workspace`; which version a tag names is `python-toolchain`. - Also when asked to containerize o
wntic/pyhouse · ★ 3 · AI & Automation · score 76
Install: claude install-skill wntic/pyhouse
# Python Container Image — the build that ships a program The image a runnable Python program ships in, written **once** per program: what goes into it, what stays out, who the process runs as and how it is told to stop. None of it recurs per feature. What the program does once it starts, and once it is told to stop, is not this skill's; where a member's image sits among several, and the compose file that runs them, is `python-workspace`. ## When to use vs. neighbours - Which version a base image, a builder image or the package manager's image names → `python-toolchain` rule 12; this skill names where those tags go, never their value. - The interpreter floor the base image has to satisfy → `python-style`, written by `python-toolchain`. - Several distributions in one repository, the compose file and one profile per runnable member → `python-workspace`; what goes inside a member's `Dockerfile` is still this skill's. - What the program reads from its environment at start-up, and the secret type that carries a credential → `python-settings`. - A comment in the `Dockerfile` or its ignore file → `python-style`'s **Comments**, which holds in every file the project writes by hand. - Where log events go, and a program whose stdout is its result → `python-logging`. - One console script per process, or per CLI app → `python-toolchain`; the image runs one of them. - What the process does once the stop signal arrives → not this skill, which only delivers the signal. - A library