Repository navigation
Add how to install extensions to the container docs - #11025
Conversation
|
@vmuzikar do you see much space for improvement? I think this guide is already enough and we can link it when we speak about the |
|
@andreaTP I think we should still do a separate "Customize and optimize Keycloak deployments using the Operator" guide. It'd be short now, just describing that you should build your custom image (with the link to this guide) and describing that auto re-augmentation is disabled if you provide a custom image. We might add in the future an explanation of the seamless augmentation. I wouldn't e.g. hide these details in the "Advanced configuration" guide. WDYT? |
|
@vmuzikar sounds good to me, changed the reference so that it won't close the issue when merged |
|
|
||
| FROM quay.io/keycloak/keycloak:latest | ||
| COPY --from=builder /opt/keycloak/lib/quarkus/ /opt/keycloak/lib/quarkus/ | ||
| COPY --from=builder /opt/keycloak/ /opt/keycloak/ |
There was a problem hiding this comment.
Is it necessary to copy full /opt/keycloak ? Can't we just copy ./lib/quarkus/ and ./providers instead?
COPY --from=builder /opt/keycloak/lib/quarkus/ /opt/keycloak/lib/quarkus/
COPY --from=builder /opt/keycloak/providers/ /opt/keycloak/providers/
There was a problem hiding this comment.
I get about ~200MB lighter image if I follow this approach instead of fully copying /opt/keycloak/
There was a problem hiding this comment.
@andreaTP any answer to that question? Would also be interested in it.
There was a problem hiding this comment.
@armujahid It should work fine because files at lib/quarkus are what really changes after a build.
If you want to send a PR with this suggestion to our guide, I'm happy to review it and make this more explicit.
Resolves #11049