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

Updates based on PR feedback

This commit is contained in:
David Currie 2015-01-09 17:23:27 +00:00
parent 1f98d6a99a
commit b9f9031ca2
2 changed files with 30 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
websphere-liberty/README-short.txt
View File

@ -1 +1 @@
Official IBM WebSphere Application Server for Developers V8.5.5 Liberty Profile image. Official IBM WebSphere Application Server for Developers Liberty Profile image.

44
websphere-liberty/content.md
View File

@ -1,9 +1,8 @@
# Overview # Overview
This image contains IBM WebSphere Application Server for Developers V8.5.5 This image contains IBM WebSphere Application Server for Developers Liberty
Liberty Profile and the IBM Java Runtime Environment 7.1 SR1. For more Profile and the IBM Java Runtime Environment. For more information on WebSphere
information on WebSphere Application Server Liberty Profile, see the Application Server Liberty Profile, see the [WASdev][getting-started] site.
[WASdev][getting-started] site.
# Usage # Usage
@ -14,14 +13,19 @@ image. You can also view the license terms by setting this variable to
`view`. Failure to set the variable will result in the termination of the `view`. Failure to set the variable will result in the termination of the
container with a usage statement. container with a usage statement.
The image is designed to support a number of different usage patterns. The following examples are based on the Liberty [application deployment sample][sample] and assume that [DefaultServletEngine.zip][zip] has been extracted to `/tmp` and the `server.xml` updated to accept connections from outside of the container by adding the following element inside the `server` stanza: The image is designed to support a number of different usage
patterns. The following examples are based on the Liberty [application
deployment sample][sample] and assume that
[DefaultServletEngine.zip][zip] has been extracted to `/tmp` and the
`server.xml` updated to accept HTTP connections from outside of the
container by adding the following element inside the `server` stanza:
``` ```
<httpEndpoint host="*" httpPort="9080" httpsPort="9443"/> <httpEndpoint host="*" httpPort="9080" httpsPort="-1"/>
``` ```
1. The image contains a default server configuration that specifies the 1. The image contains a default server configuration that specifies the
`webProfile-6.0` feature and exposes ports 9080 and 9443 for HTTP and HTTPs `webProfile-6.0` feature and exposes ports 9080 and 9443 for HTTP and HTTPS
respectively. A WAR file can therefore be mounted in to the `dropins` directory respectively. A WAR file can therefore be mounted in to the `dropins` directory
of this server and run. The following example starts a container in the of this server and run. The following example starts a container in the
background running a WAR file from the host file system with the HTTP and HTTPS background running a WAR file from the host file system with the HTTP and HTTPS
@ -36,14 +40,16 @@ ports mapped to 80 and 443 respectively.
Once the server has started, you can browse to Once the server has started, you can browse to
http://localhost/Sample1/SimpleServlet on the Docker host. http://localhost/Sample1/SimpleServlet on the Docker host.
2. For greater flexibility over configuration, it is possible to mount an entire 2. For greater flexibility over configuration, it is possible to mount
server configuration directory from the host and then specify the server name as an entire server configuration directory from the host and then
a parameter to the run command. specify the server name as a parameter to the run command. Note that
this particular example server configuration only provides HTTP
access.
``` ```
docker run -e LICENSE=accept -d -p 80:9080 -p 443:9443 \ docker run -e LICENSE=accept -d -p 80:9080 \
-v /tmp/DefaultServletEngine:/opt/ibm/wlp/usr/servers/DefaultServletEngine \ -v /tmp/DefaultServletEngine:/opt/ibm/wlp/usr/servers/DefaultServletEngine \
websphere-liberty DefaultServletEngine websphere-liberty /opt/ibm/wlp/bin/server run DefaultServletEngine
``` ```
3. It is also possible to build an application layer on top of this image using 3. It is also possible to build an application layer on top of this image using
@ -58,6 +64,13 @@ the following Dockerfile.
ENV LICENSE accept ENV LICENSE accept
``` ```
This can then be built and run as follows:
```
docker build -t app .
docker run -d -p 80:9080 -p 443:9443 app
```
4. Lastly, it is possible to mount a data volume container containing the 4. Lastly, it is possible to mount a data volume container containing the
application and the server configuration on to the image. This has the benefit application and the server configuration on to the image. This has the benefit
that it has no dependency on files from the host but still allows the that it has no dependency on files from the host but still allows the
@ -69,7 +82,7 @@ Dockerfile.
Build and run the data volume container: Build and run the data volume container:
``` ```
FROM ubuntu:14.04 FROM websphere-liberty
ADD DefaultServletEngine /opt/ibm/wlp/usr/servers/DefaultServletEngine ADD DefaultServletEngine /opt/ibm/wlp/usr/servers/DefaultServletEngine
``` ```
@ -83,8 +96,9 @@ Dockerfile.
volume container mounted: volume container mounted:
``` ```
docker run -e LICENSE=accept -d -p 80:9080 -p 443:9443 \ docker run -e LICENSE=accept -d -p 80:9080 \
--volumes-from app websphere-liberty DefaultServletEngine --volumes-from app websphere-liberty \
/opt/ibm/wlp/bin/server run DefaultServletEngine
``` ```
[getting-started]: https://developer.ibm.com/wasdev/docs/category/getting-started/ [getting-started]: https://developer.ibm.com/wasdev/docs/category/getting-started/