Chainguard Image for wildfly

WildFly is a lightweight and open-source application server designed for deploying and running Java applications.

Chainguard Images are regularly-updated, minimal container images with low-to-zero CVEs.

Download this Image

This image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/wildfly:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard registry.

Compatibility Notes

Chainguard's WildFly image is comparable to the official WildFly image. Note that, as of this writing, the entrypoint of Chainguard's WildFly image has diverged from the upstream image (quay.io/wildfly/wildfly) to bind to management interfaces over 0.0.0.0 instead of the default (-bmanagement=0.0.0.0). This change was necessary to ensure compatibility with Helm Chart version 2.4.0 (release link), as both Chainguard's image and the upstream image were failing without this modification.

This issue will be resolved once PR #143 is merged into the WildFly Charts repository.

Getting Started

To start a WildFly container using the Chainguard image, run the following command:

docker run --rm --name wildfly-container -p 9990:9990 -p 8080:8080 -it cgr.dev/ORGANIZATION/wildfly:latest

You can verify the container is running with a docker ps command:

docker ps | grep wildfly-container

To check if Wildfly has started successfully, check the logs with docker logs:

docker logs wildfly-container | grep "Started server"

You can deploy a sample WAR application to WildFly. First use curl to download a sample application from the Apache Tomcat website:

curl -sSL -o sample.war https://tomcat.apache.org/tomcat-10.1-doc/appdev/sample/sample.war

Then deploy the application:

docker cp sample.war wildfly-container:/opt/jboss/wildfly/standalone/deployments

Verify the deployment:

docker exec wildfly-container ls -l /opt/jboss/wildfly/standalone/deployments | grep sample.war

Once deployed, confirm that the sample application is accesible:

curl -s http://localhost:8080/sample/ | grep "Hello, World"

To remove the WildFly container:

docker rm -f wildfly-container

Documentation and Resources

• WildFly Quickstarts
• WildFly Guides

Contact Support

If you have a Zendesk account (typically set up for you by your Customer Success Manager) you can reach out to Chainguard's Customer Success team through our Zendesk portal.

What are Chainguard Images?

Chainguard Images are a collection of container images designed for security and minimalism.

Many Chainguard Images are distroless; they contain only an open-source application and its runtime dependencies. These images do not even contain a shell or package manager. Chainguard Images are built with Wolfi, our Linux undistro designed to produce container images that meet the requirements of a secure software supply chain.

The main features of Chainguard Images include:

• Minimal design, with no unnecessary software bloat
• Automated nightly builds to ensure Images are completely up-to-date and contain all available security patches
• High quality build-time SBOMs (software bills of materials) attesting the provenance of all artifacts within the Image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

-dev Variants

As mentioned previously, Chainguard’s distroless Images have no shell or package manager by default. This is great for security, but sometimes you need these things, especially in builder images. For those cases, most (but not all) Chainguard Images come paired with a -dev variant which does include a shell and package manager.

Although the -dev image variants have similar security features as their distroless versions, such as complete SBOMs and signatures, they feature additional software that is typically not necessary in production environments. The general recommendation is to use the -dev variants only to build the application and then copy all application artifacts into a distroless image, which will result in a final container image that has a minimal attack surface and won’t allow package installations or logins.

That being said, it’s worth noting that -dev variants of Chainguard Images are completely fine to run in production environments. After all, the -dev variants are still more secure than many popular container images based on fully-featured operating systems such as Debian and Ubuntu since they carry less software, follow a more frequent patch cadence, and offer attestations for what they include.

Learn More

To better understand how to work with Chainguard Images, we encourage you to visit Chainguard Academy, our documentation and education platform.