Dockerfile中FROM指令是否会下载基础镜像？为何构建成功后本地未显示httpd:2.4镜像

Great question! Let's unpack what's happening here step by step:

1. Docker's Layered Storage & Default Image Listing #

When you run docker-compose up -d (which triggers a build under the hood) with a FROM httpd:2.4 directive, Docker does download the httpd:2.4 base image to your local machine. However, the default docker image ls command only shows top-level images—those with a tag (like multidomainbasic_a:latest) or actively used by a running/stopped container.

The httpd:2.4 base image exists on your system as an untagged intermediate layer that your custom images (multidomainbasic_a and multidomainbasic_b) depend on. It won’t appear in the default docker image ls output unless you explicitly tag it or use it directly to start a container.

To confirm it’s present, run this command to see all images (including untagged/intermediate ones):

docker image ls -a

You’ll see an entry for httpd:2.4 (or its long image ID) listed as <none> in the repository/tag columns.

2. Is httpd:2.4 Encapsulated in Your Custom Images? #

No, it’s not "encapsulated" inside your custom images. Docker uses a layered filesystem where each image builds on top of existing layers. Your multidomainbasic_a image only contains the single layer you added: the RUN echo ... command that creates the custom index.html file. The httpd:2.4 layers are stored separately and shared between any images that use them—this is a core Docker optimization that saves disk space and speeds up builds by reusing existing layers.

You can verify this by inspecting your custom image’s layer structure:

docker inspect multidomainbasic_a

Look for the RootFS section in the output; it will list all the layer IDs that make up the image, including the layers from httpd:2.4.

3. Why the Build Succeeded Without Seeing the Base Image #

Docker automatically handles downloading base images during the build process, even if they don’t appear in the default image list. As long as the base image is available locally (either downloaded during the build or cached from a previous build), the build will complete successfully. The base image’s absence from the default docker image ls output is just a display quirk, not an indication that it’s missing.

内容的提问来源于stack exchange，提问作者ronrun