Build Tagged
container.build-tagged
Requires container builds to use an explicit image tag via -t/--tag. Untagged builds produce anonymous images that cannot be tracked or deployed.
Compatible Integrations
This guardrail works with the following integrations. Click to see how to use Build Tagged with each collector.
Enable This Guardrail
Add the parent policy to your lunar-config.yml to enable this guardrail.
policies:
- uses: github://earthly/lunar-lib/policies/container@v1.0.0
include: [build-tagged]
# with: ...How This Guardrail Works
This guardrail is part of the Container Guardrails policy. It evaluates data collected by integrations and produces a pass/fail check with actionable feedback.
When enabled, this check runs automatically on every PR and in AI coding workflows, providing real-time enforcement of your engineering standards.
Learn How Lunar Works →Configuration Options
These inputs can be configured in your lunar-config.yml to customize
how the parent policy (and this guardrail) behaves.
| Input | Required | Default | Description |
|---|---|---|---|
allowed_registries
|
Optional |
docker.io
|
Comma-separated list of allowed registries |
required_labels
|
Required | — | Comma-separated list of required labels checked across Dockerfile and build commands (empty = no requirement) |
Container Guardrails
This guardrail is part of the Container Guardrails policy, which includes 7 guardrails for devex build and ci.
Ready to Automate Your Standards?
See how Lunar can turn your engineering wiki, compliance docs, or postmortem action items into automated guardrails with our 100+ built-in guardrails.
Infrastructure conventions
Post-mortem action items
Security & compliance policies
Testing & quality requirements