A developer prepares a local sidewalk-inspection tool image before any registry push. Which statement matches the build–tag–run lifecycle?
Select an answer to reveal the explanation.
Short Explanation
Build makes the blueprint copy, tag gives it a name on the shelf, run starts one working copy. Turning off the working copy does not shred the blueprint—and deleting the blueprint does not erase the recipe file on disk.
Full Explanation
Local lifecycle: docker build produces an image, tagging names it for discovery, and docker run starts a container from that image. Stopping a container leaves the image intact; removing an image does not delete the Dockerfile source. Push and pull belong to the registry step, not this local cycle.