WildFly 17 S2I image on quay.io
Starting with WildFly 17, the WildFly S2I Docker image is now accessible from quay.io at this URL: https://quay.io/repository/wildfly/wildfly-centos7
A companion image, a WildFly runtime Docker image that allows you to chain builds in OpenShift or use Docker multi stage builds, is available from: https://quay.io/repository/wildfly/wildfly-runtime-centos7
For a complete documentation on how to use these images using s2i, OpenShift and Docker, refer to this documentation.
WildFly 17 S2I image and the WildFly Operator
WildFly S2I implementation notes
This image offers the same features that were provided by the WildFly 16 image. In addition, during S2I build you have now the ability to provision a WildFly server using Galleon.
Documentation on how to configure S2I build and WildFly server execution can be found there.
Chaining builds with runtime image
In order to benefit from OpenShit chained builds or docker multi stage builds to build an application image that only contains what is required to execute WildFly (S2I tooling being removed), we have introduced a docker wildfly-runtime-centos7 image into which you can copy the WildFly server and deployed application from the WildFly S2I generated application image.
This OpenShift template automates the chained builds to output a smaller application image.
Adding imagestreams and template to OpenShift
At some point the new images will be made available from OpenShift catalog and image repository. You can already use these images by adding them yourselves to your OpenShift cluster.
WildFly S2I builder image stream: oc create -f https://raw.githubusercontent.com/wildfly/wildfly-s2i/wf-17.0/imagestreams/wildfly-centos7.json
WildFly runtime image stream: oc create -f https://raw.githubusercontent.com/wildfly/wildfly-s2i/wf-17.0/imagestreams/wildfly-runtime-centos7.json
Chained build template: oc create -f https://raw.githubusercontent.com/wildfly/wildfly-s2i/wf-17.0/templates/wildfly-s2i-chained-build-template.yml
NB: If you import the image streams in your project, be sure to set ImageStreams Namespace to your project namespace in the template. openshift being the default namespace.