Hi @nb_glur , indeed, it looks like the jboss/keycloak repository has been deprecated and should be replaced with quay.io/keycloak/keycloak. It may be possible to fix this by editing the relevant config line in the docker-compose.yaml file generated by the eaasi-installer (even after a partial/failed deployment, it should be located under /opt/eaasi, if I’m reading your EaaSI configuration correctly from the systemctl status output)
i.e. edit:
keycloak:
image: jboss/keycloak: 15.0.2
to:
keycloak:
image: quay.io/keycloak/keycloak: 15.0.2
That specific 15.0.2 container should still be available in that repo, so with luck it should be pulled and everything else will proceed as expected.
If issues continue to persist, we are in the process of examining dependency issues throughout the stack as part of a wider effort to craft a more maintainable release, so our ability to support deployments of these older versions and components of the codebase from ~2021 or earlier will be extremely limited. We hope to have much more recent/updated code available for test purposes soon, perhaps by the end of the year.
@nb_glur, by chance are you attending the iPres conference in Ghent next week? We will be hosting an EaaSI-related “Birds of a Feather” discussion session there and it would be lovely to connect on your experiments with EaaSI and the status of our program and the software moving forward if so