dockerfile-fix

Dockerfile Fix Skill

Fix Dockerfile issues discovered by runtime verification (batch_verify.sh). This skill diagnoses actual import failures, version conflicts, and missing dependencies from verify_result.txt, then repairs the Dockerfile, updates packages.json, and optionally fixes scripts when packages are unavailable.

Input

User provides:

1. task_package_path: Path to the task package directory (containing problem/, evaluation/, environment/)
2. dockerfile_name (optional): Name of the Dockerfile to fix. Default: Dockerfile.v3. Can also be Dockerfile or any other name.

Prerequisites

The following files must exist in {task_package_path}/environment/:

• verify_result.txt — output from batch_verify.sh, with status "has failures" or "build failed"
• packages.json — package manifest (see environment_guide.md Step 4)
• {dockerfile_name} — the Dockerfile to fix

Reference Materials

Read these before starting:

• environment_guide.md — Dockerfile generation logic, known compatibility issues, Script-First Rule, version conflict handling
• Dockerfile.base.v3 — base image packages and versions
• base_packages.json — base package list with import names

Procedure

Phase 1: Diagnose

1. Carry-forward check (mandatory before diagnosis): if dockerfile_fix_log.txt already records prior fix rounds for this Dockerfile, diff the current Dockerfile.v3 against the prior round's fixes. If the current Dockerfile is missing pins/RUN steps that earlier rounds added, the verify pipeline regressed to an earlier Dockerfile state — first re-merge all prior fixes into the current Dockerfile, then proceed to diagnose only the new failures. Do not start diagnosing fresh as if no history exists; you will keep re-deriving the same fixes round after round.