dockerignore behaving differently in podman vs docker

[thomasmattheussen]

I have the following dockerignore which produces different results when building with podman vs building with docker.

*
!packages/my-theme-*/package.json

and a directory listing such as

packages/my-theme-a/package.json
packages/my-theme-b/package.json
packages/my-theme-c/package.json

You can easily test by running this command (once with docker and once with podman)

docker build --no-cache --progress plain --file - . <<EOF
FROM busybox
COPY . /build-context
WORKDIR /build-context
RUN find .
EOF

When using docker, it does what I would expect (exclude everything except those files). When using podman, it just excludes everything. It seems as though the files I mentioned in dockerignore are somehow not matched.

I have tried several patterns such as these below but none seem to actually work.

!packages/**/package.json

!**/package.json

(I'm using the latest podman 5.1.1)

[nalind]

Huh. It looks like .dockerignore behavior change between the "classic" builder and the BuildKit-based one - I get the same results if I run the docker build with DOCKER_BUILDKIT=0 set in my environment. We're going to want to match the newer behavior sooner or later, though.

[rhatdan]

Yes I think we should default ot matching buildkit

[thomasmattheussen]

Thanks for your reply! Not sure how to fix my problem though 😅
I'd like for my podman build to get the same results as with the docker build. It seems the wildcard matching just isn't working correctly right now, or am I misunderstanding something?

[afbjorklund]

You can use buildkit with podman, but unfortunately not with podman buildx

https://github.com/moby/buildkit#podman

[landsman]

It just does not work, do not respect .dockerignore at all 😢

• using docker compose (/Users/landsman/bin/docker-compose).
• I got the same results with podman-compose

podman-compose version 1.3.0
podman version 5.3.2