This is an example Dockerfile with WildFly application server.
To boot in standalone mode
docker run -it ppavlov/wildfly
To boot in standalone mode with admin console available remotely
docker run -p 8080:8080 -p 9990:9990 -it ppavlov/wildfly /opt/jboss/wildfly/bin/standalone.sh -bmanagement 0.0.0.0
To boot in domain mode
docker run -it ppavlov/wildfly /opt/jboss/wildfly/bin/domain.sh -b 0.0.0.0 -bmanagement 0.0.0.0
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/standalone/deployments/
or /opt/jboss/wildfly/domain/deployments/
depending on which mode you choose (standalone is default in the ppavlov/wildfly
image -- see above).
The simplest and cleanest way to deploy an application to WildFly running in a container started from the ppavlov/wildfly
image is to use the deployment scanner method mentioned above.
To do this you just need to extend the ppavlov/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 (RUN
command).
A simple example was prepared to show how to do it, but the steps are following:
-
Create
Dockerfile
with following content:FROM ppavlov/wildfly ADD your-awesome-app.war /opt/jboss/wildfly/standalone/deployments/
-
Place your
your-awesome-app.war
file in the same directory as yourDockerfile
. -
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.