tofu-tools¶
OpenTofu CI image: tofu, tflint (+ pre-baked AWS ruleset), terraform-docs. Derives from ci-base.
Release v0.1.6, 2026-11-04. Built on ci-base. Source: phpboyscout/images/tofu-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 |
Later releases (v0.1.7) are tagged but have no image, because their publish was held, so this page describes v0.1.6.
About this image¶
The OpenTofu track's CI image.
Contains tofu, tflint (with the AWS ruleset pre-baked) and
terraform-docs, on top of ci-base.
Three tools, where infra-tools carried eight¶
| Dropped | Why |
|---|---|
| trivy, gitleaks, checkov | tofu-security now runs its scanners in pinned upstream single-purpose images (cicd !224), matching go-/rust-/svelte-security. |
| aws-cli (257 MB) | No component invokes aws — the tofu-* components authenticate through the Tofu AWS provider's own OIDC path. |
phpboyscout/sandbox does call the AWS CLI, but pins infra-tools directly,
which keeps publishing through the deprecation cycle.
No mise¶
Tools are installed from their upstream release assets, each pinned by an
annotated ARG that Renovate tracks, each verified against the checksum file
its upstream publishes.
mise was measured against this when the image was written and lost: a slower cold build for no smaller an image, two Renovate managers against one, GitHub API version-resolution against plain release downloads, and no checksum verification at all. The raw timings were not kept and the mise variant is not in history, so the comparison is recorded by outcome rather than by number.
Note the tools disagree on every packaging detail: opentofu ships a versioned
zip with SHA256SUMS, tflint an unversioned zip with checksums.txt, and
terraform-docs a versioned tar.gz with a single-line .sha256sum. That
inconsistency is the real cost of dropping a resolver, and it is spelled out in
the Dockerfile rather than hidden.
Why not Wolfi's apk packages¶
They scan far cleaner — 6 gate-visible findings against 74, because Wolfi rebuilds against a current Go toolchain — and they were rejected.
Wolfi lags. Checked 2026-09-14, its opentofu-1.12 package provides 1.12.1
against the OPENTOFU_VERSION pinned in the Dockerfile, and that gap holds
three published OpenTofu advisories, including a HIGH arbitrary file read during
git operations (GHSA-q7j3-v8qv-22vq, fixed in 1.12.3). Trading real,
directly-exploitable advisories for a better-looking scan report is the wrong
way round.
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 |
Go binaries from upstream releases | advisory |
If scan:os is red, we can fix it: bump the ci-base digest or the package.
It measured zero when written.
scan:tools carries stdlib advisories from whatever Go each maintainer built
with — terraform-docs v0.24.0, the latest release, is built with Go 1.25.8,
well behind the Go go-tools pins. No pin fixes that; only an upstream
rebuild does. infra-tools and dev-tools soft-fail their whole scan for
this reason, which also silences the half that is actionable.
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.