Hacker News new | ask | show | jobs
by andersonmvd 3550 days ago
That's very exciting news. I still find somewhat confusing to execute "RUN" instructions, as they're much cleaner in Linux, but I need to dig the documentation. However there is a line that caught my attention:

> This flexibility comes at the cost of some bulk: The `microsoft/windowsservercore` image takes up 10GB.

Hope next versions shrink the image size.

> And the Nano Server base image is an order of magnitude smaller than Windows Server Core, meaning it has less dependencies and surface area to keep updated.

I wonder how smaller it is. Do you have any estimate here?

2 comments

If it's really a order of magnitude I'd expect it to be 1 gig.
The `docker pull` payload is 358MB: https://hub.docker.com/r/microsoft/nanoserver/tags/
It's 800MB.
What's the storage backend being used on Windows? With even an 800MiB base, let alone 10GiB, I'm curious what happens when creating 100 containers from that base? On Linux, whether the backend is device mapper (thin), overlayfs, or Btrfs, the snapshots are fast and the cost is only the change from the base.
Docker running on Windows comes with the same layering and CoW semantics as on Windows. If you're curious about the details, John Starks' session at DockerCon is really great: https://www.youtube.com/watch?v=85nCF5S8Qok