6:03 p.m.
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?
6:07 p.m.
What's the reason for moving to Quay?
Cheers,
Thomas
Stian Thorgersen <sthorger(a)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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
8:12 p.m.
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(a)googlemail.com>
wrote:
What's the reason for moving to Quay?
Cheers,
Thomas
Stian Thorgersen <sthorger(a)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(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>
8:14 p.m.
Right now the images are available both on Quay and Docker Hub. With
potentially removing Docker Hub in the future.
You can find the images in Quay here:
https://quay.io/organization/keycloak
In Quay it's keycloak/keycloak instead of jboss/keycloak as we do want to
get away from the false impression that Keycloak is only for Java stuff.
On Thu, 7 Mar 2019 at 12:12, Stian Thorgersen <sthorger(a)redhat.com> wrote:
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(a)googlemail.com> wrote:
> What's the reason for moving to Quay?
>
> Cheers,
> Thomas
>
> Stian Thorgersen <sthorger(a)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(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>>
>
8:16 p.m.
From my impression most distros already pull images from quay
automatically, so there shouldn't be any change for the user. For those few
that don't have distros where it pulls from quay the images can be pulled
with docker pull quay.io/keycloak/keycloak
On Thu, 7 Mar 2019 at 12:14, Stian Thorgersen <sthorger(a)redhat.com> wrote:
Right now the images are available both on Quay and Docker Hub. With
potentially removing Docker Hub in the future.
You can find the images in Quay here:
https://quay.io/organization/keycloak
In Quay it's keycloak/keycloak instead of jboss/keycloak as we do want to
get away from the false impression that Keycloak is only for Java stuff.
On Thu, 7 Mar 2019 at 12:12, Stian Thorgersen <sthorger(a)redhat.com> wrote:
> 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(a)googlemail.com> wrote:
>
>> What's the reason for moving to Quay?
>>
>> Cheers,
>> Thomas
>>
>> Stian Thorgersen <sthorger(a)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(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>>>
>>
1888
days inactive
1888
days old
4 comments
2 participants
participants (2)
-
Stian Thorgersen -
Thomas Darimont