Hi,

I'll move forward to move our WildFly Docker image to quay.io at https://quay.io/repository/wildfly/wildfly

I tried different approaches and we will use a GitHub action to build the image and push it to quay.io (instead of having quay.io monitor new tags from the GitHub repository).

I've opened the PR for it at https://github.com/jboss-dockerfiles/wildfly/pull/151

I've created the quay.io repository for the image at https://quay.io/repository/wildfly/wildfly and populate it with existing images from the latest 3 major versions of WildFly (25.0.0.Final, 24.0.0.Final, 23.0.2.Final).

In order to bootstrap the process, I'll also retag 25.0.1.Final (after the PR is merged) so that the new GitHub action will build and push the 25.0.1.Final image (and tag is as latest too).

best regards,

jeff

On Wed, Oct 20, 2021 at 9:32 AM Jean-Frederic Mesnil <jmesnil@redhat.com> wrote:

> On 20 Oct 2021, at 09:28, Harald Pehl <hpehl@redhat.com> wrote:
>
> What about images for WildFly versions < 25.0.0.Final Would they be available on hub.docker.com, quay.io or both?
>

We won’t touch hub.docker.com so the existing images there will stay available.

It’s also reasonable to push some of the more recent versions (e.g. 23, 24).

I was not planning on pushing all existing images from hub.docker.com to quay.io but anything that can make the transition seamless is up for discussion.

Best regards,
Jeff

--
Jeff Mesnil
Principal Software Engineer
Red Hat
http://jmesnil.net/