-
Notifications
You must be signed in to change notification settings - Fork 85
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
Error: creating /etc/mtab symlink: invalid argument #433
Comments
what is the underlying filesystem on |
btrfs |
thanks. I am still not able to reproduce locally. Can you please share the output of |
thanks, still not able to reproduce here, even on Debian. Was the store created by the same rootless user? |
Oh yes. Clean run. Acutally I'm using my own 'proton' script to fetch and build proton.
|
wonder if it is caused by fuse-overlayfs. Any reason for using it instead of native overlay? |
root permission ofc. fuse-overlayfs for compiling proton root-less |
you can use native overlay with rootless too |
With disabled:
I got same:
|
you need to reset the store. Once |
Indeed it works with native overlayfs. Still a mystery to me how does overlayfs does not require root permission, but ok. I'll keep it issue open, right? |
native overlay works from a user namespace since linux v5.10. I'll move it to fuse-overlayfs |
Build process of podman root-less environment failed because of lack of permissions. For example the following command failed:
But If I run same command without podman (or It could be same issue affecting creating symlink under fuse-overlayfs. I guess |
could you please run strace on the fuse-overlayfs to see what syscall is failing? Run strace on fuse-overlayfs, run the failing command, then stop strace. Something like:
|
Not sure what PID you are asking for. I ran |
I even ran this: And "Yes" I'm running updated storage with 'mount_program' set, so I'm getting "Error: creating /etc/mtab symlink: invalid argument". I guess here is no fuse-overlayfs process started yet. |
that is strange. So are you getting the error from Can you run |
|
I am confused now, is there any To catch the
Is that podman command running on the host or are you in a nested container? |
Here are two prefixes 1) fuse 2) native. First time you told me to try fuse, last time you ask me to use native ("without any underlying fuse-overlayfs"). Right? So I did. No podman running during test cp runs. |
if you running You can try with |
It does. Same error. |
yeah it looks like a similar error:
|
|
Issue Description
podman failed to initialize rootless storage.
Steps to reproduce the issue
Steps to reproduce the issue:
Describe the results you received
Error: creating /etc/mtab symlink: invalid argument
Describe the results you expected
storage successfully initialized
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
No
Additional environment details
Debian Trixie
Additional information
Happens everytime.
The text was updated successfully, but these errors were encountered: