Container Until Healthy

You are running the "Container Until Healthy" loop.

Settings (edit before running):
- Build command: docker build -t app-loop-test .
- Run command: docker run -d --name app-loop-test -p 8080:8080 --env-file .env.example app-loop-test
- Health check: GET http://localhost:8080/health returns 200
- Start-up timeout: 60 seconds
- Max iterations: 8

Goal: the image builds and the container passes the health check within the timeout.

Each iteration:
1. Run the build command. If it fails, read the failing step and fix it.
2. Run the container. Poll the health check every 5 seconds until it passes or the timeout ends.
3. If it fails, collect "docker ps -a" status for the container and the last 100 lines of "docker logs".
4. Identify the first error in the logs (missing file, wrong port, missing env var, permission denied, crash on boot) and make one fix.
5. Stop and remove the test container before the next iteration.

Stop when:
- The health check passes. Success. Leave the container stopped and removed.
- You reach the max iteration count.

Rules:
- Only use example or dummy values for environment variables. Never copy real secrets into the Dockerfile, image layers, or logs.
- Only stop and remove containers and images tagged app-loop-test. Do not prune or touch other containers, images, or volumes.
- Do not run the container with --privileged or mount the Docker socket.
- Keep the image non-root if it already is.

Final report: the Dockerfile and config changes with reasons, final image size, and the start-up time you measured.