max / alloy

Stop the Containerfile claiming the image is published Line 3 has said "Published to quay.io/alloy/alloy" since before the 2026-07-30 decision that distribution is the builder and not the artifact. docs/STACK.md:13 and docs/IMAGE.md:61 were corrected in that pass and this was missed, so the file that builds the image was the one place still stating it ships to a registry. Matches the language the other two already use: not merely unpublished today, not a future address.

Author: Max Johnson <me@maxj.phd> · 2026-08-01 17:16 UTC

Signed with PGP, not checked

Commit: 088b1eed311377a9ddb6d8f6dbf9cc94ad2d0350

Parent: 89a4d42

1 file changed, +3 insertions, -1 deletion

M Containerfile +3 -1

			@@ -1,6 +1,8 @@
1	1		# Alloy — bootable container image
2	2		#
3		-	# Built with `podman build`. Published to quay.io/alloy/alloy.
	3	+	# Built with `podman build`. Nothing is published: distribution is the builder
	4	+	# and not the artifact, so `quay.io/alloy/alloy` is not a future address either
	5	+	# (decided 2026-07-30; docs/STACK.md#distribution, docs/IMAGE.md).
4	6		# See docs/IMAGE.md for the composition strategy and rationale.
5	7		#
6	8		# Layer order optimizes rebuild speed: repos first (rarely change),