- Docker on Windows
- Elton Stoneman
- 228字
- 2021-07-02 12:47:57
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.
- Ansible權(quán)威指南
- Instant Handlebars.js
- RESS Essentials
- Instant Optimizing Embedded Systems using Busybox
- 移動應用UI設(shè)計模式(第2版)
- Linux自動化運維:Shell與Ansible(微課版)
- 巧學活用Windows 7
- VMware NSX Cookbook
- ElasticSearch Cookbook
- Learning BeagleBone
- Windows Server 2008組網(wǎng)技術(shù)與實訓(第3版)
- BuddyPress Theme Development
- 電腦辦公(Windows 7+Office 2016)入門與提高
- 電腦辦公(Windows 7 + Office 2013)入門與提高
- 程序員必讀經(jīng)典(算法基礎(chǔ)+計算機系統(tǒng))