[keycloak-dev] Moving container images to Quay (from Docker Hub)

Stian Thorgersen sthorger at redhat.com
Thu Mar 7 06:12:36 EST 2019


Docker has gained too much ownership around containers. Red Hat is doing a
lot of investments around improving that to give people flexibility and
choices when it comes to containers. This includes Podman, Buildah and
Quay.io. That being said it is obviously still important for us that
container images are still available to those that choose to use Docker
tools, so we will make sure you still can docker run keycloak.

Any reason why not Quay?! ;)

On Thu, 7 Mar 2019 at 10:07, Thomas Darimont <thomas.darimont at googlemail.com>
wrote:

> What's the reason for moving to Quay?
>
> Cheers,
> Thomas
>
> Stian Thorgersen <sthorger at redhat.com> schrieb am Do., 7. März 2019,
> 10:04:
>
>> We are planning on moving our container images to Quay.io. The question is
>> do we also need to keep pushing to Docker Hub? If so why?
>> _______________________________________________
>> keycloak-dev mailing list
>> keycloak-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>>
>


More information about the keycloak-dev mailing list