-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"lstat: invalid argument" when using 'overlay' storage driver with fuse-overlayfs #9006
Comments
lstat: invalid argument
when using 'overlay' storage driver
Edit: This does not end up using So that was weird. I tried removing the storage.conf, and it started working. Perplexed by this, I decided to diff the output of
It appears that the
entry in the The working Do note the
|
The storage options got moved to specific drivers, here:
BTW; I think "overlay2" is for docker, it got called "overlay" in podman |
Reopening this, since running the |
I compared the output of a working install on a Ubuntu server and there seems to be something weird going on: Working log:
Broken log:
As you can see, the 'broken' one never reaches |
I believe this is fixed in podman 3.0. With newer kernels, we should be able to get rootless overlay working without fuse-overlay as well. |
@rhatdan I just confirmed this still happens with |
Just recreated this on a fresh build of
Debug log
|
@giuseppe PTAL |
Tested with kernel |
Isolated this to a |
let's follow up on the fuse-overlayfs issue |
nevermind my last comment. The error:
happens in Podman. Could you run something like:
and show the output? What file system are you using for Since both this issue and the one reported for fuse-overlayfs happen on Gentoo, I guess it is something related to it |
@giuseppe Here is the strace log, doesn't seem to have anything interesting. My whole drive is using ext4. I have really no clue what could be causing this. I've tested multiple
I have also attached a strace of manually running a Strace log
Manual fuse-overlayfs invocation
|
This issues was resolved for me by upgrading fuse-overlayfs to 1.7.1 -- you might wanna check with that one @Ristovski |
@apollo13 Indeed! This got fixed in containers/fuse-overlayfs#316, I forgot to bump this issue. |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Running podman in rootless mode with the
overlay
(oroverlay2
, they are the same from what I can tell) storage driver (withfuse-overlayfs
) fails.Steps to reproduce the issue:
podman container run --rm -it hello-world
Describe the results you received:
Running anything with overlayfs on Gentoo causes the following error:
I modified
container_internal.go
to exit as soon as it hits that error (to prevent any cleanup),and the container [id] directory ends up containing only the following items:
in storage driver directory:
(note the
hello
binary being present)Additional information you deem important (e.g. issue happens only occasionally):
vfs
storage driver works just fineOutput of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
Physical Gentoo Linux
storage.conf
:The text was updated successfully, but these errors were encountered: