Run update.sh

This commit is contained in:
Docker Library Bot 2019-05-14 23:13:41 +00:00
parent 085978f62a
commit 15ebace26e
3 changed files with 9 additions and 1 deletions

View File

@ -17,7 +17,7 @@ WARNING:
# Supported tags and respective `Dockerfile` links
- [`3.3.2`, `3.3`, `latest` (*Dockerfile*)](https://github.com/crate/docker-crate/blob/446fb7cd0c7060a34364da76d771fcd51fc4e090/Dockerfile)
- [`3.2.7`, `3.2` (*Dockerfile*)](https://github.com/crate/docker-crate/blob/daf383f50a6369415bd7f83a220395caef2e561e/Dockerfile)
- [`3.2.8`, `3.2` (*Dockerfile*)](https://github.com/crate/docker-crate/blob/cd46c51f77fabac4abd60ca29f7da82faaaf2b5f/Dockerfile)
- [`3.1.6`, `3.1` (*Dockerfile*)](https://github.com/crate/docker-crate/blob/f15504034e1d0ea67d4517daec2ff4adf1435d65/Dockerfile)
- [`3.0.7`, `3.0` (*Dockerfile*)](https://github.com/crate/docker-crate/blob/ca1f030be8be51c126fa908400aa031be6eb0412/Dockerfile)
- [`2.3.11`, `2.3` (*Dockerfile*)](https://github.com/crate/docker-crate/blob/f15780fc923017c66040c4baf79f2efd506655ac/Dockerfile)

View File

@ -138,6 +138,10 @@ It is a very strong best practice to create an extending Docker image, we called
If you want to build the smallest possible WebSphere Liberty application image you can start with our `kernel` tag, add your artifacts, and run `configure.sh` to grow the set of features to be fit-for-purpose. Please see our [GitHub page](https://github.com/OpenLiberty/ci.docker#building-an-application-image) for more details.
## Enabling Enterprise functionality
The Open Liberty images have a set of built-in XML snippets that enable and configure enterprise functionality such as session cache and monitoring. These are toggled by specific `ARG`s in your application image Dockerfile and configured via the `configure.sh` script. Please see the [instructions](https://github.com/openliberty/ci.docker#enterprise-functionality) on our GitHub page for more information.
## Using volumes for configuration
This pattern can be useful for quick experiments / early development (i.e. `I just want to run the application as I iterate over it`), but should not be used for development scenarios that involve different teams and environments - for these cases the `Application Image` pattern described above is the way to go.

View File

@ -155,6 +155,10 @@ It is a very strong best practice to create an extending Docker image, we called
If you want to build the smallest possible WebSphere Liberty application image you can start with our `kernel` tag, add your artifacts, and run `configure.sh` to grow the set of features to be fit-for-purpose. Please see our [GitHub page](https://github.com/WASdev/ci.docker#building-an-application-image) for more details.
## Enabling Enterprise functionality
The WebSphere Liberty images have a set of built-in XML snippets that enable and configure enterprise functionality such as session cache and monitoring. These are toggled by specific `ARG`s in your application image Dockerfile and configured via the `configure.sh` script. Please see the [instructions](https://github.com/wasdev/ci.docker#enterprise-functionality) on our GitHub page for more information.
## Using volumes for configuration
This pattern can be useful for quick experiments / early development (i.e. `I just want to run the application as I iterate over it`), but should not be used for development scenarios that involve different teams and environments - for these cases the `Application Image` pattern described above is the way to go.