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.

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

Set memory limit for Keycloak container #1350

Closed
mabartos opened this issue Oct 1, 2024 · 0 comments · Fixed by #1351
Closed

Set memory limit for Keycloak container #1350

mabartos opened this issue Oct 1, 2024 · 0 comments · Fixed by #1351

Comments

@mabartos
Copy link
Contributor

mabartos commented Oct 1, 2024

As mentioned in the issue quarkusio/quarkus#43601 (comment), the memory limit for Keycloak container should be set, otherwise, there's an expected rapid increase of memory usage. For more information, see the mentioned issue/PR.

Even for the Quarkus test framework, the memory limit should be set, otherwise OOM can be seen - as reported here: quarkusio/quarkus#43630.

mabartos added a commit to mabartos/quarkus-test-framework that referenced this issue Oct 1, 2024
mabartos added a commit to mabartos/quarkus-test-framework that referenced this issue Oct 2, 2024
fedinskiy pushed a commit to fedinskiy/quarkus-test-framework that referenced this issue Oct 7, 2024
Closes quarkus-qe#1350

Signed-off-by: Martin Bartoš <[email protected]>
(cherry picked from commit 2b907f1)
fedinskiy pushed a commit that referenced this issue Oct 8, 2024
Closes #1350

Signed-off-by: Martin Bartoš <[email protected]>
(cherry picked from commit 2b907f1)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant