You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
buildah version 1.38.0 (image-spec 1.1.0, runtime-spec 1.2.0)
When using --layers --cache-to ... --cache-from ... I'm seeing buildah store cached layers for every single directive in the file. This includes things like ENV, CMD, LABEL, WORKDIR, ENTRYPOINT. These directives have no effect on the actual filesystem and it definitely takes way more time to cache them than it would be to recompute them.
I noticed this behavior as I'm coming from kaniko where it did not cache these types of changes and buildah stores many more cached layers and is executing slower as a result.
Example dockerfile:
FROM public.ecr.aws/docker/library/python:3.9.20-bookworm
CMD ["/bin/bash"]
ENV PYTHONUNBUFFERED=1
ENV UV_PYTHON_PREFERENCE=system
ENV UV_PYTHON_DOWNLOADS=0
ENV DEBIAN_FRONTEND=noninteractive
RUN apt-get update
<snip />
buildah version 1.38.0 (image-spec 1.1.0, runtime-spec 1.2.0)
When using
--layers --cache-to ... --cache-from ...
I'm seeing buildah store cached layers for every single directive in the file. This includes things likeENV
,CMD
,LABEL
,WORKDIR
,ENTRYPOINT
. These directives have no effect on the actual filesystem and it definitely takes way more time to cache them than it would be to recompute them.I noticed this behavior as I'm coming from kaniko where it did not cache these types of changes and buildah stores many more cached layers and is executing slower as a result.
Example dockerfile:
Example with buildah:
Example using kaniko:
Some rough timings from pipelines I'm seeing:
The text was updated successfully, but these errors were encountered: