Q: Your CI pipeline runs unit tests inside a Docker build using a multi-stage Dockerfile. If the tests fail, you want to extract the test report (JUnit XML) from the failed build stage. But `docker build` exits with an error and produces no final image. How do you get the test report out?
Use the --target flag to build only up to the test stage, and structure the Dockerfile so the test report is generated *before* the assertion that causes the build to fail: Build with: docker build --target test -o.
--target flag.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third.""
Want to master this scenario in a live sandbox? KodeKloud's Docker Certified Associate (DCA) Hands-On Lab Course covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "During an image optimization initiative across our services, we solved this exact problem. The interviewer is testing: Multi-stage build targets, --target flag.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Production Solution & Architecture
Use the --target flag to build only up to the test stage, and structure the Dockerfile so the test report is generated *before* the assertion that causes the build to fail: Build with: docker build --target test -o type=local,dest=./output . using BuildKit's --output flag. Even if the full build fails, you can separately export just the test stage output. Alternatively, use docker create on the test target image and docker cp the report out.
FROM golang:1.21 AS test
COPY . .
RUN go test -v ./... -count=1 2>&1 | go-junit-report > /report.xml; \
go test ./... -count=1
FROM alpine AS runtime
COPY --from=test /app/binary /app/binary
- Immediate Triage: Use the --target flag to build only up to the test stage, and structure the Dockerfile so the t
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
-
Structuring Dockerfile instructions inefficiently by copying app source before package manifests when configuring pipeline runs unit
Copying code before package manifests (
package.json,go.mod,requirements.txt) invalidates the build cache on every commit, forcing slow full reinstalls. -
Neglecting the PID 1 process reap problem and omitting proper SIGTERM signal forwarding when configuring pipeline runs unit
If an application runs as PID 1 without an init system (like
tini), it fails to reap zombie child processes and ignoresSIGTERMsignals, causing unclean 10s timeouts. - Assembling single-stage images containing compilers, build SDKs, and header files in production when configuring pipeline runs unit Single-stage builds bloat image size by gigabytes and expose extensive package vulnerabilities; multi-stage builds isolate artifacts into minimal distroless images.
- Confusing container port forwarding on bridge networks with unisolated host networking mode when configuring pipeline runs unit Bridge networking utilizes iptables NAT translations which add latency overhead, whereas host networking bypasses the network namespace entirely.