Docker Compose Linter

Store Positioning

Store title: Docker Compose Linter

Short description: Lint Docker Compose YAML files for structure, service configuration issues, portability problems, risky defaults, missing health checks, unpinned images, exposed ports, volume concerns, and production-readiness warnings.

SEO title: Docker Compose Linter — technical SEO, web, and domain audit

SEO description: Lint Docker Compose YAML files for structure, service configuration issues, portability problems, risky defaults, missing health checks, unpinned images, exposed ports, volume concerns, and production-readiness warnings. Use it to find crawlability, indexability, security, metadata, and page-quality issues with evidence-backed rows and audit reports.

Categories: SEO_TOOLS, ECOMMERCE

Keywords: docker, compose, linter, web/domain audit

Pay-Per-Event Pricing

This actor uses pay-per-event pricing. Event prices include Apify platform usage; users are not expected to pay a separate platform-usage pass-through charge for the configured pricing model.

• Tier: W1 — Web/domain audit
• Primary event: page-audited at $0.00490 base
• Default max charge: $10.00
• Store discounts: FREE/BRONZE base, SILVER discounted, GOLD deepest approved discount

Event set:

• actor-start: base $0.00500, GOLD $0.00400. Docker Compose Linter: charged when actor start is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• page-audited: base $0.00490, GOLD $0.00392. Docker Compose Linter: charged when page audited is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• record-extracted: base $0.00372, GOLD $0.00298. Docker Compose Linter: charged when record extracted is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• finding-emitted: base $0.00372, GOLD $0.00298. Docker Compose Linter: charged when finding emitted is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• audit-report-generated: base $0.05000, GOLD $0.04000. Docker Compose Linter: charged when audit report generated is completed. The price includes Apify platform usage; no separate usage pass-through is intended.

The actor accepts actor-start before work, accepts the primary event before each dataset row, and accepts the configured report event before writing report files. If maxChargeUsd or the live PPE limit blocks a charge, the corresponding row or report is not written.

Public Task Concepts

• Audit Docker Compose controls on a capped public sample
• Find high-priority Docker Compose issues before release
• Validate Docker Compose evidence from supplied pages
• Prioritize Docker Compose fixes with severity and proof
• Export Docker Compose QA rows for client review

Lint Docker Compose YAML files for structure, service configuration issues, portability problems, risky defaults, missing health checks, unpinned images, exposed ports, volume concerns, and production-readiness warnings.

What it does

• Accept raw Compose YAML, public file URLs, repository file URLs, or uploaded file contents.
• Parse Compose files safely without running containers.
• Inspect services, images, ports, volumes, networks, environment variables, secrets, health checks, restart policies, depends-on usage, build contexts, profiles, and extension fields.
• Emit issue rows with severity, rule ID, YAML path, evidence, and recommendation.
• Generate service inventory and lint summary reports.
• Support strict, balanced, and advisory lint profiles.

What it does not do

• No container execution, Docker daemon access, image vulnerability scanning, secret exfiltration, or deployment certification.
• No private repository access unless content is supplied.

Input fields

Primary inputs from the locked actor spec: composeFiles, composeUrls, repositoryFileUrls, lintProfile, enabledRules, disabledRules, treatWarningsAsFailures, includeServiceInventory, includePortInventory, includeVolumeInventory, maxFiles, timeoutMs. maxChargeUsd keeps runs capped during production use.

Output fields

Dataset rows include: sourceId, sourceUrl, filePath, composeProjectName, serviceName, ruleId, issueCategory, severity, yamlPath, message, recommendation, evidence, lineNumber, lintProfile, passed.

Starter example

Use examples/input.tiny.json as a small starter input. Keep the first run capped and review the dataset before increasing limits.

Public task examples

• Run Docker Compose Linter on supplied sample data: Run Docker Compose Linter on supplied sample data using a small bounded input.
• Generate a Docker Compose Linter QA report: Generate a Docker Compose Linter QA report using a small bounded input.
• Find invalid rows with Docker Compose Linter: Find invalid rows with Docker Compose Linter using a small bounded input.
• Create a capped local endpoint readiness check for Docker Compose Linter: Create a capped local endpoint readiness check for Docker Compose Linter using a small bounded input.
• Prepare Docker Compose Linter output for downstream automation: Prepare Docker Compose Linter output for downstream automation using a small bounded input.

Public source provenance

The starter input audits Docker's public awesome-compose example at immutable commit 30f4b7f6a6c3b0c0ecf4d4efb0de203c48d11562. Public tasks use five files from that same revision, so each result is traceable to a real upstream Compose configuration.

Reports

• docker-compose-lint-report.md
• compose-service-inventory.json
• compose-port-inventory.csv
• compose-volume-inventory.csv
• compose-lint-summary.json

Limitations and safe use

Start with supplied-input runs, then enable live endpoints only with tight caps, domain allowlists, and no secrets in public examples.