Am 07.10.23 um 14:18 schrieb Daniel Walsh:
On 10/6/23 15:07, Tom Sweeney wrote:
> Hi Leon,
>
> What OS, OS version, and Podman/Buildah versions are you using?
>
> t
>
> On 10/6/23 15:02, Leon Fauster via Podman wrote:
>> Hi all, I'm doing my first steps with podman and friends - so,
>> bear with me.
>>
>> I was expecting the same results between buildah bud vs
>> podman build while creating an image with a Containerfile.
>> I noticed that the podman's artifact has a layer more then
>> buildah's one:
>>
>> podman:
>>
>> "Data": {
>> "LowerDir": "...1ef8/diff",
>> "UpperDir": "...2a81/diff",
>> "WorkDir": "...2a81/work"
>> }
>>
>> buildah:
>>
>> "Data": {
>> "UpperDir": "...b9918/diff",
>> "WorkDir": "...b9918/work"
>> }
>>
>>
>> Podmans additional layer has the outcome of:
>>
>> RUN adduser --no-create-home --home-dir /app --shell /bin/bash -u
>> 1000 user
>>
>> separated while buildah has merged it into the "base".
>>
>> Is this the normal behavior or which knob should I use for a
>> consistency output?
>>
> _______________________________________________
> Podman mailing list -- podman(a)lists.podman.io
> To unsubscribe send an email to podman-leave(a)lists.podman.io
One difference between podman buildah and buildah bud is --layers
$ podman build --help | grep -- --layers
podman build --layers --force-rm --tag imageName .
--layers cache intermediate
layers during build. Use BUILDAH_LAYERS environment variable to
override. (default true)
Versus
$ buildah bud --help | grep -- --layers
--layers cache intermediate
layers during build. Use BUILDAH_LAYERS environment variable to override.
(Buildah defaults --layers=false, while podman build defaults
--layers=true)
Ok, I got it. I had read it before (man page) but had the impression
that its only relevant for the build process (caching to speed up).
I didn't expect that the result (image) would inheriting the same layer
structure. Maybe the explanation in the manual pages is not quite clear
(ambiguous) or I read it that way ... thought.
--
Thanks
Leon