Yesterday, my Jenkins pipeline could install dependencies and build the frontend. But there was a missing piece: Docker. Without it, I couldn't package my applications into containers — the whole point of this challenge! Today, I fixed that. I configured Jenkins to build Docker images for both my backend and frontend, turning my CI pipeline into a complete build system. First: Why Docker in CI? Before Docker in CI The pipeline could: Pull code from GitHub Install dependencies Build the frontend Could NOT create Docker images After Docker in CI The pipeline can: Pull code from GitHub Install dependencies Build the frontend Create Docker images for backend AND frontend Why this matters: Docker images are what actually get deployed to production. Without them, you can't run your app anywhere else. Step 1: Giving Jenkins Docker Access The Problem Jenkins runs in a container. By default, containers can't access the host's Docker daemon.…