History

Tianon Gravi 0c2b9dcce8 Refactor the way information (especially links) are presented This should make it much faster to find the right place to file issues, get help, find out whether upstream maintains an image, etc. I've done my best to represent each `REPO/maintainer.md` file appropriately, but I might have missed some (or there might be something else a maintainer prefers be listed there, either more or less descriptive, for example), which would be welcome contributions following this change.	2017-04-21 17:48:19 -07:00
..
README-short.txt	Add a bunch more content	2014-10-10 18:07:15 -06:00
README.md	Update "scratch" and "hello-world" to be more complimentary	2015-05-14 12:14:44 -06:00

Tianon Gravi 0c2b9dcce8 Refactor the way information (especially links) are presented

This should make it much faster to find the right place to file issues, get help, find out whether upstream maintains an image, etc.

I've done my best to represent each `REPO/maintainer.md` file appropriately, but I might have missed some (or there might be something else a maintainer prefers be listed there, either more or less descriptive, for example), which would be welcome contributions following this change.

2017-04-21 17:48:19 -07:00

README-short.txt

Add a bunch more content

2014-10-10 18:07:15 -06:00

README.md

Update "scratch" and "hello-world" to be more complimentary

2015-05-14 12:14:44 -06:00

README.md

`FROM scratch`

This image is most useful in the context of building base images (such as debian and busybox) or super minimal images (that contain only a single binary and whatever it requires, such as hello-world).

As of Docker 1.5.0 (specifically, docker/docker#8827), FROM scratch is a no-op in the Dockerfile, and will not create an extra layer in your image (so a previously 2-layer image will be a 1-layer image instead).