Is a finding a release blocker or an accepted exception?
Review line-level Dockerfile findings against the application's needs. Record the reason and owner for each retained warning instead of chasing a zero-warning score.
Elysia Tools
Navigation
Workflow playbook
Review Dockerfile findings, validate image references, expose duplicate environment keys and explain staging-to-production drift in one container release record.
New to this workflow? Follow the steps in order, starting with the first tool below. Already know what you need? Jump straight to the matching step — every tool in this workflow is listed in the comparison table.
First tool: Dockerfile Linter & Best-Practices Checker
Hubs
| Tool | What it does | Category |
|---|---|---|
| Dockerfile Linter & Best-Practices Checker | Hadolint-style static analysis for Dockerfiles without a Docker daemon: 30+ rules across image pinning, package-manager hygiene, layer caching, secrets and signal handling, with severities, line numbers and fix examples. | Development |
| Docker Image Tag Validator | Validate Docker image names and tags according to Docker naming conventions | Validation |
| .env Parser | Extract and validate .env style KEY=VALUE configurations with detection of duplicate keys and suspicious spaces/quotes | Data Processing |
| .env File Validator | Validate .env files for syntax errors and common issues |
Hubs
| Validation |
| Environment Config Diff Visualizer | Compare dev, staging, and production configuration bundles across JSON, YAML, TOML, or ENV formats and highlight drift, missing keys, and cleanup suggestions | Development |
This workflow helps an application maintainer prepare a container release review. Keep the Dockerfile, image reference and environment snapshots tied to one revision. Mixing an old staging file with a new production file creates false drift. Write the required-key checklist from application expectations, including ports, service endpoints and feature flags. Sanitize secrets before using any shared tool while preserving key names and meaningful nonsecret values. Keep secret-change status in an appropriate private record; identical placeholders do not demonstrate identical credentials. For a fuller disclosure review, use pii-log-redaction.
Use only sanitized copies; replace sensitive values before pasting or uploading. Env Parser and Env File Validator can return input values. Diff masking applies only to displayed values for matching key names; it does not sanitize inputs.
Use dockerfile-linter to inspect line-level findings around base-image pinning, package hygiene, user selection and configuration embedded in the build. Resolve relevant findings or record the reason and owner of an exception. The tool does not build the image or scan its installed dependencies. Check base and application references with docker-image-tag-validator, then record the actual artifact identity from CI. A legal repository and tag string cannot prove that the registry contains it or that the target machine can pull and execute it.
Dockerfile Linter runs a fixed set of static rules and reproduces the submitted source in the report. Use a sanitized Dockerfile; do not treat a clean report as a build, dependency scan or approval.
Use Docker Image Tag Validator as a preliminary syntax check. It does not validate the digest against any image or verify the reference with a registry. Check the exact artifact identity, platform and pull results separately in approved CI.
Run env-parser on sanitized text before reducing configuration to a map, because a map may already have discarded duplicate definitions. Resolve duplicates according to the intended value and check unusual quotes or spaces against the application loader. Use env-file-validator for another syntax review and compare the resulting key list with required keys. Tool validation does not prove precedence across process variables, mounted files and application defaults; verify the effective values in the test environment without exposing secrets.
Use Env Parser on sanitized text to review duplicate occurrences and formatting before exporting: map exports keep the last parsed value per key. Env File Validator checks basic syntax and optional quote, empty-value and duplicate rules, not your required-key list. Compare keys manually and confirm behavior with the target loader.
Put staging and production blocks into environment-config-diff-visualizer using its named environment headers. Mark each difference as intended, corrected or still open. A production hostname may be expected; a missing database key or a leftover debug flag needs a decision. Attach Dockerfile findings, reference checks, duplicate resolutions and the classified diff to the same revision. Before approving deployment, attach actual CI build, pull and startup results as separate evidence. For configuration conversion or merging, continue with config-workflows; broader infrastructure identifier checks belong in network-infrastructure-identifier-format-checks.
Use two or more sanitized blocks with headers of the form === label (format) ===. The diff can flag missing keys or unequal parsed values, but its dotenv map keeps the last value for a repeated key and does not apply application defaults. Resolve duplicates first and use the target parser to confirm changes.
Workflow playbook
Dockerfile Linter runs a fixed set of static rules and reproduces the submitted source in the report. Use a sanitized Dockerfile; do not treat a clean report as a build, dependency scan or approval.
Use Docker Image Tag Validator as a preliminary syntax check. It does not validate the digest against any image or verify the reference with a registry. Check the exact artifact identity, platform and pull results separately in approved CI.
Use Env Parser on sanitized text to review duplicate occurrences and formatting before exporting: map exports keep the last parsed value per key. Env File Validator checks basic syntax and optional quote, empty-value and duplicate rules, not your required-key list. Compare keys manually and confirm behavior with the target loader.
Review line-level Dockerfile findings against the application's needs. Record the reason and owner for each retained warning instead of chasing a zero-warning score.
Use Docker Image Tag Validator as a preliminary syntax check. It does not validate the digest against any image or verify the reference with a registry. Check the exact artifact identity, platform and pull results separately in approved CI.
Classify hostnames, ports and feature flags against the agreed environment policy. Keep missing required keys and unexplained values open until resolved.
Use two or more sanitized blocks with headers of the form `=== label (format) ===`. The diff can flag missing keys or unequal parsed values, but its dotenv map keeps the last value for a repeated key and does not apply application defaults. Resolve duplicates first and use the target parser to confirm changes.