Supported tags and respective
WildFly Docker image
To boot in standalone mode
docker run -it andreptb/wildfly
To boot in domain mode
docker run -it andreptb/wildfly /opt/jboss/wildfly/bin/domain.sh -b 0.0.0.0 -bmanagement 0.0.0.0
What are the differences between this image and jboss/wildfly?
- Uses andreptb/oracle-java instead of jboss/base-jdk:7.
- Provides base images with Oracle JDK 7 and 8.
With the WildFly server you can deploy your application in multiple ways:
- You can use CLI
- You can use the web console
- You can use the management API directly
- You can use the deployment scanner
The most popular way of deploying an application is using the deployment scanner. In WildFly this method is enabled by default and the only thing you need to do is to place your application inside of the
deployments/ directory. It can be
/opt/jboss/wildfly/domain/deployments/ depending on which mode you choose (standalone is default in the
andreptb/wildfly image -- see above).
The simplest and cleanest way to deploy an application to WildFly running in a container started from the
andreptb/wildfly image is to use the deployment scanner method mentioned above.
To do this you just need to extend the
andreptb/wildfly image by creating a new one. Place your application inside the
deployments/ directory with the
ADD command (but make sure to include the trailing slash on the deployment folder path, more info). You can also do the changes to the configuration (if any) as additional steps (
A simple example was prepared to show how to do it, but the steps are following:
Dockerfilewith following content:
FROM andreptb/wildfly ADD your-awesome-app.war /opt/jboss/wildfly/standalone/deployments/
- Place your
your-awesome-app.warfile in the same directory as your
- Run the build with
docker build --tag=wildfly-app .
- Run the container with
docker run -it wildfly-app. Application will be deployed on the container boot.
This way of deployment is great because of a few things:
- It utilizes Docker as the build tool providing stable builds
- Rebuilding image this way is very fast (once again: Docker)
- You only need to do changes to the base WildFly image that are required to run your application
Logging can be done in many ways. This blog post describes a lot of them.
Sometimes you need to customize the application server configuration. There are many ways to do it and this blog post tries to summarize it.
Extending the image
To be able to create a management user to access the administration console create a Dockerfile with the following content
FROM andreptb/wildfly RUN /opt/jboss/wildfly/bin/add-user.sh admin Admin#70365 --silent CMD ["/opt/jboss/wildfly/bin/standalone.sh", "-b", "0.0.0.0", "-bmanagement", "0.0.0.0"]
Then you can build the image:
docker build --tag=andreptb/wildfly-admin .
docker run -it -p 9990:9990 andreptb/wildfly-admin
The administration console should be available at http://localhost:9990.
This image is based on the popular Alpine Linux project, available in the
alpine official image. Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
This variant is highly recommended when final image size being as small as possible is desired. See this Hacker News comment thread for more discussion of the issues that might arise and some pro/con comparisons of using Alpine-based images.
To minimize image size, it's uncommon for additional related tools (such as
bash) to be included in Alpine-based images. Using this image as a base, add the things you need in your own Dockerfile (see the
alpine image description for examples of how to install packages if you are unfamiliar).
View license information for the software contained in this image.
Supported Docker versions
This image is officially supported on Docker version 1.6.2.
If you have any problems with or questions about this image, please contact me through a GitHub issue.