using mount program /usr/local/bin/fuse-overlayfs: unknown argument ignored: lazytime

[pinghe]

v5.5.1

runs-on: ubuntu-latest
container:
  image: ghcr.io/mgoltzsche/podman:5.5.1
  options: --privileged --security-opt seccomp=unconfined

...

- name: build & push image
  run: |
    podman images
    podman build -t "podman:v5.5.1"  -f ./Dockerfile .

log:
Writing manifest to image destination
time="2025-06-13T04:08:03Z" level=error msg="Unmounting /var/lib/containers/storage/overlay/a94b37757ba35e01c1582608563090b44b92f25f709531866c35d2dc31760d9d/merged: invalid argument"
Error: mounting new container: mounting build container "1bef6629f70e36f97d3e3be889798d2580851cdb32d0bd703b09739e3ee5dd97": creating overlay mount to /var/lib/containers/storage/overlay/a94b37757ba35e01c1582608563090b44b92f25f709531866c35d2dc31760d9d/merged, mount_data="....,nodev,fsync=0,volatile": using mount program /usr/local/bin/fuse-overlayfs: unknown argument ignored: lazytime

[mgoltzsche]

I remember also having seen that error not long ago somewhere but unfortunately I missed to capture it within a bug ticket and now I cannot reproduce it locally on an Ubuntu 24.04 host (which should correspond to the GHA runner VM image).

Can you please provide a reproducible example?
Maybe something like this:

printf 'FROM alpine:3.22\nRUN echo hello' | podman run -i --rm --privileged mgoltzsche/podman:5.5.1 podman build -f - .

Though, I cannot reproduce the problem this way - also not when using the Dockerfile within the repo:

podman run -ti --rm --privileged -v "`pwd`:/src" -w /src mgoltzsche/podman:5.5.1 podman build -t test .

Alternatively, if you cannot reproduce it otherwise, you could post here a complete but minimal GHA workflow that reproduces it.
However, in case you can only reproduce the problem within the GHA workflow, then the reason for that might be that another binary version within a shared bin dir takes precedence within the GHA environment or that GHA forces the container to run as UID 1001 (which the podman container image is not prepared for by default).

Did you try the same using the official fedora-based podman image? Does it work using that image?
if it doesn't work with the official image (outside a GHA workflow), you should create a corresponding issue within the upstream podman repo, in case there isn't such an issue already.
Actually, did you search the upstream podman and buildah repositories for issues related to your problem?

I found some related ones:

• Unprivileged buildah container fails to build image with fuse: device not found, try 'modprobe fuse' first fuse-overlayfs: cannot mount: No such file or directory podman-container-tools/buildah#5456
• [Bug]: Unable to use Native Overlayfs - Podman reverts back to fuse-overlayfs podman-container-tools/podman#17057