instruction: Create a Dockerfile for fundamentals
output: ```dockerfile
  from the same exact image, the total size on disk for
  these containers would be SUM (size of containers) plus one image size
  (virtual size - size).This also doesn't count the following additional ways a container can take up
  disk space:Disk space used for log files stored by the
  logging-driver.
  This can be non-trivial if your container generates a large amount of logging
  data and log rotation isn't configured.Volumes and bind mounts used by the container.Disk space used for the container's configuration files, which are typically
  small.Memory written to disk (if swapping is enabled).Checkpoints, if you're using the experimental checkpoint/restore feature.The copy-on-write (CoW) strategyCopy-on-write is a strategy of sharing and copying files for maximum efficiency.
  If a file or directory exists in a lower layer within the image, and another
  layer (including the writable layer) needs read access to it, it just uses the
  existing file. The first time another layer needs to modify the file (when
  building the image or running the container), the file is copied into that layer
  and modified. This minimizes I/O and the size of each of the subsequent layers.
  These advantages are explained in more depth below.Sharing promotes smaller imagesWhen you use docker pull to pull down an image
  ```