官术网_书友最值得收藏!

Understanding temporary containers and image state

My website container has an ID that starts with 6e3d, which is the hostname that the application inside the container should see, but that's not what the website claims. So, what went wrong? Remember that Docker executes every build instruction inside a temporary, intermediate container.

The RUN instruction to generate the HTML ran in a temporary container, so the PowerShell script wrote that container's ID as the hostname in the HTML file; this is where the container ID starting with bf37 came from. The intermediate container gets removed by Docker, but the HTML file it created persists within the image.

This is an important concept: when you build a Docker image, the instructions execute inside temporary containers. The containers are removed, but the state they write persists within the final image and will be present in any containers you run from that image. If I run multiple containers from my website image, they will all show the same hostname from the HTML file, because that's saved inside the image, which is shared by all containers.

Of course, you can also store the state in individual containers, which is not part of the image, so it's not shared between containers. I'll look at how to work with data in Docker now and then finish the chapter with a real-world Dockerfile example.

主站蜘蛛池模板: 怀来县| 康保县| 麻栗坡县| 凉城县| 灌云县| 驻马店市| 嵊泗县| 南丰县| 浦县| 金塔县| 林西县| 内丘县| 湖北省| 珲春市| 阿瓦提县| 镇安县| 南雄市| 泉州市| 罗平县| 五河县| 奇台县| 休宁县| 达州市| 射洪县| 白河县| 长春市| 千阳县| 克什克腾旗| 芜湖县| 恩施市| 孝义市| 云南省| 连州市| 鄯善县| 梅州市| 大荔县| 神农架林区| 浙江省| 新巴尔虎右旗| 柞水县| 东方市|