docker-library
/
docs
mirror of https://github.com/docker-library/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Run update.sh

This commit is contained in:
Docker Library Bot 2015-12-11 20:20:45 +00:00
parent cce143e297
commit 2a33dad7b2
9 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
erlang/README.md
View File

@ -63,7 +63,7 @@ The `erlang` images come in many flavors, each designed for a specific use case.
## `erlang:<version>` ## `erlang:<version>`
This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of. This tag is based off of [`buildpack-deps`](https://registry.hub.docker.com/_/buildpack-deps/). `buildpack-deps` is designed for the average user of docker who has many images on their system. It, by design, has a large number of extremely common Debian packages. This reduces the number of packages that images that derive from it need to install, thus reducing the overall size of all images on your system. This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
## `erlang:onbuild` ## `erlang:onbuild`

2
golang/README.md
View File

@ -82,7 +82,7 @@ The `golang` images come in many flavors, each designed for a specific use case.
## `golang:<version>` ## `golang:<version>`
This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of. This tag is based off of [`buildpack-deps`](https://registry.hub.docker.com/_/buildpack-deps/). `buildpack-deps` is designed for the average user of docker who has many images on their system. It, by design, has a large number of extremely common Debian packages. This reduces the number of packages that images that derive from it need to install, thus reducing the overall size of all images on your system. This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
## `golang:alpine` ## `golang:alpine`

4
hello-world/README.md
View File

@ -33,8 +33,8 @@ For more examples and ideas, visit:
$ docker images hello-world $ docker images hello-world
REPOSITORY TAG IMAGE ID SIZE REPOSITORY TAG IMAGE ID VIRTUAL SIZE
hello-world latest 690ed74de00f 960 B hello-world latest 0a6ba66e537a 960 B
``` ```
![logo](https://raw.githubusercontent.com/docker-library/docs/master/hello-world/logo.png) ![logo](https://raw.githubusercontent.com/docker-library/docs/master/hello-world/logo.png)

4
hello-world/content.md
View File

@ -25,8 +25,8 @@ For more examples and ideas, visit:
$ docker images hello-world $ docker images hello-world
REPOSITORY TAG IMAGE ID SIZE REPOSITORY TAG IMAGE ID VIRTUAL SIZE
hello-world latest 690ed74de00f 960 B hello-world latest 0a6ba66e537a 960 B
``` ```
%%LOGO%% %%LOGO%%

2
iojs/README.md
View File

@ -57,7 +57,7 @@ The `iojs` images come in many flavors, each designed for a specific use case.
## `iojs:<version>` ## `iojs:<version>`
This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of. This tag is based off of [`buildpack-deps`](https://registry.hub.docker.com/_/buildpack-deps/). `buildpack-deps` is designed for the average user of docker who has many images on their system. It, by design, has a large number of extremely common Debian packages. This reduces the number of packages that images that derive from it need to install, thus reducing the overall size of all images on your system. This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
## `iojs:onbuild` ## `iojs:onbuild`

2
node/README.md
View File

@ -68,7 +68,7 @@ The `node` images come in many flavors, each designed for a specific use case.
## `node:<version>` ## `node:<version>`
This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of. This tag is based off of [`buildpack-deps`](https://registry.hub.docker.com/_/buildpack-deps/). `buildpack-deps` is designed for the average user of docker who has many images on their system. It, by design, has a large number of extremely common Debian packages. This reduces the number of packages that images that derive from it need to install, thus reducing the overall size of all images on your system. This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
## `node:onbuild` ## `node:onbuild`

2
pypy/README.md
View File

@ -66,7 +66,7 @@ The `pypy` images come in many flavors, each designed for a specific use case.
## `pypy:<version>` ## `pypy:<version>`
This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of. This tag is based off of [`buildpack-deps`](https://registry.hub.docker.com/_/buildpack-deps/). `buildpack-deps` is designed for the average user of docker who has many images on their system. It, by design, has a large number of extremely common Debian packages. This reduces the number of packages that images that derive from it need to install, thus reducing the overall size of all images on your system. This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
## `pypy:onbuild` ## `pypy:onbuild`

2
python/README.md
View File

@ -77,7 +77,7 @@ The `python` images come in many flavors, each designed for a specific use case.
## `python:<version>` ## `python:<version>`
This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of. This tag is based off of [`buildpack-deps`](https://registry.hub.docker.com/_/buildpack-deps/). `buildpack-deps` is designed for the average user of docker who has many images on their system. It, by design, has a large number of extremely common Debian packages. This reduces the number of packages that images that derive from it need to install, thus reducing the overall size of all images on your system. This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
## `python:onbuild` ## `python:onbuild`

2
ruby/README.md
View File

@ -65,7 +65,7 @@ The `ruby` images come in many flavors, each designed for a specific use case.
## `ruby:<version>` ## `ruby:<version>`
This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of. This tag is based off of [`buildpack-deps`](https://registry.hub.docker.com/_/buildpack-deps/). `buildpack-deps` is designed for the average user of docker who has many images on their system. It, by design, has a large number of extremely common Debian packages. This reduces the number of packages that images that derive from it need to install, thus reducing the overall size of all images on your system. This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
## `ruby:onbuild` ## `ruby:onbuild`