Repository navigation
Podman optimized image layer size #39176
Replies: 2 comments 2 replies
I'm not sure. Can you provide the full image size differences between docker and podman?
I believe that should work, along with anything you may want from conf. |
|
Since my first message, I updated base image to keycloak 26.2.1 and a few custom files, so now the last layers in dive show 2.7MB (buildx) vs 172MB (podman). And keycloak withpodman cd3d48c857af About a minute ago 623MB
keycloak withbuildx 844168b60b5b 2 minutes ago 454MBThanks for your answer, I will go with the multiple COPY |
|
That's good to know. We have started some docs around known issues with Docker, it looks like we may need to do the same with podman. cc @ASzc do you have any insight here about COPY operations with podman? |
|
I haven't heard of this before. Since podman operates in a non-root environment there may potentially be some compromises with detecting changed files. If image size is a major priority I would recommend writing the dockerfile to be more precise in what gets COPY'd |
Uh oh!
There was an error while loading. Please reload this page.
Hello,
I found that building a optimized docker image with podman instead of docker make the layer bigger.
The
COPY --from=builder /opt/keycloak/ /opt/keycloak/layer with podman seems to include unmodified files too.When using
wagoodman/diveto inspect the layer:docker (buildx):
2.6 MB COPY /opt/keycloak/ /opt/keycloak/ # buildkitpodman:
164 MB #(nop) COPY dir:d5205e2f652ffeddd3ebdc35ff9aedce12ad58ec65cb22718a89518d77855c78 in /opt/keycloak/Is there any way to not have a layer so big with podman?
Is it OK to only copy
/opt/keycloak/lib/quarkusand the providers and themes I added?All reactions