Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Keycloak cannot be restarted #1439

Closed
dlebrero opened this issue May 25, 2018 · 0 comments
Closed

Keycloak cannot be restarted #1439

dlebrero opened this issue May 25, 2018 · 0 comments

Comments

@dlebrero
Copy link
Contributor

When Keycloak is restarted it throws an exception similar to https://issues.jboss.org/browse/KEYCLOAK-4754?attachmentViewMode=list&_sscc=t

Restart happens if you do a docker-compose stop, restart or if you ^C
dlebrero added a commit that referenced this issue May 25, 2018
@dlebrero
[#1439] Using IGNORE_EXISTING when importing
09ed316 
It means that if the default akvo.json is changed the KC container must
be recreated (or the whole dev env) but it also means that any change
in the realm is not lost when restarting the container, which is more
in line with how the Postgres DB actually works.
@dlebrero dlebrero mentioned this issue May 25, 2018
Merged
iperdomo added a commit that referenced this issue May 26, 2018
@iperdomo
Merge pull request #1440 from akvo/issue/1439-kc-fails-on-restart
94e33ea 
[#1439] Using IGNORE_EXISTING when importing
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dlebrero