[keycloak-dev] Keycloak docker image diverged between master and latest
Schuster Sebastian (INST-CSS/BSV-OS2)
Sebastian.Schuster at bosch-si.com
Thu Jul 18 09:02:18 EDT 2019
Thanks a lot, that is pretty much as expected.
Any chance we could also have the master branch available at quay.io? ☺
Best regards,
Sebastian
Mit freundlichen Grüßen / Best regards
Dr.-Ing. Sebastian Schuster
Open Source Services (INST-CSS/BSV-OS2)
Bosch Software Innovations GmbH | Ullsteinstr. 128 | 12109 Berlin | GERMANY | www.bosch-si.com<http://www.bosch-si.com>
Tel. +49 30 726112-485 | Mobil +49 152 02177668 | Fax +49 30 726112-100 | Sebastian.Schuster at bosch-si.com<mailto:Sebastian.Schuster at bosch-si.com>
Sitz: Berlin, Registergericht: Amtsgericht Charlottenburg; HRB 148411 B
Aufsichtsratsvorsitzender: Dr.-Ing. Thorsten Lücke; Geschäftsführung: Dr. Stefan Ferber, Michael Hahn, Dr. Aleksandar Mitrovic
Von: Stian Thorgersen <sthorger at redhat.com>
Gesendet: Donnerstag, 18. Juli 2019 14:58
An: Schuster Sebastian (INST-CSS/BSV-OS2) <Sebastian.Schuster at bosch-si.com>
Cc: keycloak-dev <keycloak-dev at lists.jboss.org>
Betreff: Re: [keycloak-dev] Keycloak docker image diverged between master and latest
Resolved now - latest is set to be identical to 6.0.1.
On Thu, 18 Jul 2019 at 14:54, Stian Thorgersen <sthorger at redhat.com<mailto:sthorger at redhat.com>> wrote:
That's not intentional. Looking at it now it seems PRs have been sent to latest rather than master.
latest should be identical to 6.0.1. It's just there as a convenience to get Docker Hub to build a latest tag automatically. Ideal would be to just tag the 6.0.1 image, but that is a lot more work to automate.
On Wed, 17 Jul 2019 at 17:20, Schuster Sebastian (INST-CSS/BSV-OS2) <Sebastian.Schuster at bosch-si.com<mailto:Sebastian.Schuster at bosch-si.com>> wrote:
I was assuming that “latest” is completely contained in “master”, i.e. it points to an older commit of the master branch.
Currently, it points to a commit that is not in master: https://github.com/jboss-dockerfiles/keycloak/commit/ec4b1d3ff80e4d792c4f202c5b98275db42e45a7
while missing older commits that are in master. It’s also not identical to the 6.0.1 tag, which is the latest release.
It looks a bit like it is maintained independently from master?
Best regards,
Sebastian
Mit freundlichen Grüßen / Best regards
Dr.-Ing. Sebastian Schuster
Open Source Services (INST-CSS/BSV-OS2)
Bosch Software Innovations GmbH | Ullsteinstr. 128 | 12109 Berlin | GERMANY | www.bosch-si.com<http://www.bosch-si.com>
Tel. +49 30 726112-485 | Mobil +49 152 02177668 | Fax +49 30 726112-100 | Sebastian.Schuster at bosch-si.com<mailto:Sebastian.Schuster at bosch-si.com>
Sitz: Berlin, Registergericht: Amtsgericht Charlottenburg; HRB 148411 B
Aufsichtsratsvorsitzender: Dr.-Ing. Thorsten Lücke; Geschäftsführung: Dr. Stefan Ferber, Michael Hahn, Dr. Aleksandar Mitrovic
Von: Stian Thorgersen <sthorger at redhat.com<mailto:sthorger at redhat.com>>
Gesendet: Mittwoch, 17. Juli 2019 17:06
An: Schuster Sebastian (INST-CSS/BSV-OS2) <Sebastian.Schuster at bosch-si.com<mailto:Sebastian.Schuster at bosch-si.com>>
Cc: keycloak-dev <keycloak-dev at lists.jboss.org<mailto:keycloak-dev at lists.jboss.org>>
Betreff: Re: [keycloak-dev] Keycloak docker image diverged between master and latest
latest points to the latest stable release. While master is just a developer build and should be considered unstable.
On Wed, 17 Jul 2019 at 16:25, Schuster Sebastian (INST-CSS/BSV-OS2) <Sebastian.Schuster at bosch-si.com<mailto:Sebastian.Schuster at bosch-si.com>> wrote:
Hi Keycloak Devs,
We are currently using the Keycloak docker image hosted on quay: https://quay.io/repository/keycloak/keycloak
Since we need to use the tcp stack for Jgroups, we need the feature introduced here: https://github.com/jboss-dockerfiles/keycloak/commit/b4a1fa301114ec08b70861d1cc6241ac8c85ef4a
However, I noticed this commit is not included in the “latest” tag. Looking at the branch latest (https://github.com/jboss-dockerfiles/keycloak/commits/latest) I noticed it has actually diverged
from “master” and misses the commit we need.
Is this a bug or a feature? What is the general idea of the “latest” branch compared to the “master” branch?
Thanks and best regards,
Sebastian
Mit freundlichen Grüßen / Best regards
Dr.-Ing. Sebastian Schuster
Open Source Services (INST-CSS/BSV-OS2)
Bosch Software Innovations GmbH | Ullsteinstr. 128 | 12109 Berlin | GERMANY | www.bosch-si.com<http://www.bosch-si.com><http://www.bosch-si.com>
Tel. +49 30 726112-485 | Mobil +49 152 02177668 | Fax +49 30 726112-100 | Sebastian.Schuster at bosch-si.com<mailto:Sebastian.Schuster at bosch-si.com><mailto:Sebastian.Schuster at bosch-si.com<mailto:Sebastian.Schuster at bosch-si.com>>
Sitz: Berlin, Registergericht: Amtsgericht Charlottenburg; HRB 148411 B
Aufsichtsratsvorsitzender: Dr.-Ing. Thorsten Lücke; Geschäftsführung: Dr. Stefan Ferber, Michael Hahn, Dr. Aleksandar Mitrovic
_______________________________________________
keycloak-dev mailing list
keycloak-dev at lists.jboss.org<mailto:keycloak-dev at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/keycloak-dev
More information about the keycloak-dev
mailing list