Run update.sh

This commit is contained in:
Docker Library Bot 2017-01-17 16:45:48 -08:00
parent 113c1c2d69
commit a00df01992
2 changed files with 2 additions and 2 deletions

View File

@ -1,6 +1,6 @@
# Supported tags and respective `Dockerfile` links # Supported tags and respective `Dockerfile` links
- [`3.10.1.1`, `latest` (*Dockerfile*)](https://github.com/aerospike/aerospike-server.docker/blob/c54477af5e0b62f506d5234dca012db63c906224/Dockerfile) - [`3.11.0.2`, `latest` (*Dockerfile*)](https://github.com/aerospike/aerospike-server.docker/blob/02bb550eaa05935b5ddc30df943f5245d91819d8/Dockerfile)
For more information about this image and its history, please see [the relevant manifest file (`library/aerospike`)](https://github.com/docker-library/official-images/blob/master/library/aerospike). This image is updated via [pull requests to the `docker-library/official-images` GitHub repo](https://github.com/docker-library/official-images/pulls?q=label%3Alibrary%2Faerospike). For more information about this image and its history, please see [the relevant manifest file (`library/aerospike`)](https://github.com/docker-library/official-images/blob/master/library/aerospike). This image is updated via [pull requests to the `docker-library/official-images` GitHub repo](https://github.com/docker-library/official-images/pulls?q=label%3Alibrary%2Faerospike).

View File

@ -44,7 +44,7 @@ This stack is designed to be the foundation of a language-stack image.
## What's included? ## What's included?
The main tags of this image are the full batteries-included approach. With them, a majority of arbitrary `gem install` / `npm install` / `pip install` should be successfull without additional header/development packages. The main tags of this image are the full batteries-included approach. With them, a majority of arbitrary `gem install` / `npm install` / `pip install` should be successful without additional header/development packages.
For some language stacks, that doesn't make sense, particularly if linking to arbitrary external C libraries is much less common (as in Go and Java, for example), which is where these other smaller variants can come in handy. For some language stacks, that doesn't make sense, particularly if linking to arbitrary external C libraries is much less common (as in Go and Java, for example), which is where these other smaller variants can come in handy.