4 ms·

docker images REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE windowsservercore latest 9eca9231f4d4 30 hours ago 9.613 GB

docker images REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE windowsservercore latest 9eca9231f4d4 30 hours ago 9.613 GB windowsservercore 10.0.10254.0 9eca9231f4d4 30 hours ago 9.613 GB vs REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE alpine latest 31f630c65071 9 weeks ago 5.254 MB Aren't containers supposed to be small(er)?

aikah 11y ago
Is it a container or an image ? it looks like some image for VM with some kind of bootstrapping for linux or something. And what is the license for a Windows Server Core ? Is it possible to find a ELI5 for how it is supposed to work ?
- chris-at 11y ago
  It's a container image (output from docker images). see https://msdn.microsoft.com/virtualization/windowscontainers/quick_start/manage_docker https://msdn.microsoft.com/virtualization/windowscontainers/...
scooley 11y ago
Don’t worry. This is an early build and you’ll see things get smaller in future updates :). *I work for Microsoft on these specifically.
- bpye 11y ago
  Is this going to be through use of nano server for the container images I guess? Or something you cannot yet share.
  - scooley 11y ago
    Bingo.
codemac 11y ago
No, they aren't supposed to be anything. Docker added this concept of a "graphdriver" where things are stored as their delta on disk as they assume you'll use many of them. Obviously your first windows container is gonna use up more blocks in that type of storage than a linux container built specifically to be small[0] [0]: http://gliderlabs.viewdocs.io/docker-alpine/ http://gliderlabs.viewdocs.io/docker-alpine/