-
Notifications
You must be signed in to change notification settings - Fork 787
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
overlay/overlay2 not supported by kernel 4.20.3 or extfs? #1304
Comments
There is a bug somewhere, I erased Also, there is no |
@TomasTomecek work as expected with overlay, or did it change your config to vfs? |
I think your issue is a dupe of containers/podman#2172 Overlay. I don't use vfs, it is slow and inefficient. |
The overlay driver is doing some testing to see if the file system as full support on file system it is attempting to use. Could you turn on full debugging to see if containers/storage gives you more information on why it says the storage is not working? |
This fails in this function. What is the file system that this is happening on, It is being reported as extfs.
|
It's happening on ext4, as reported. I notice now this only happens when running buildah as a regular user (buildah-in-a-user-namespace). I'll include the comment-stripped [storage]
driver = "overlay"
runroot = "/var/run/containers/storage"
graphroot = "/var/lib/containers/storage"
[storage.options]
additionalimagestores = [
]
size = ""
override_kernel_check = "true"
mountopt = "nodev"
[storage.options.thinpool]
ostree_repo = ""
skip_mount_home = "false" Back to regular user: buildah --debug images
Maybe I haven't properly configured user namespace stuff. What I've done:
|
Well, Fedora workstation and Cloud image uses ext4 as the default rootfs. Many other distros use ext4 as default too. I don't see any reasons podman should not support ext4. |
Do you have fuse-overlayfs installed on your box? |
I can get something like this to happen if I have a bogus entry in ~/.config/containers/storage.conf
If you remove this and install fuse-overlayfs does the problem go away? |
Overlayfs is not supported in rootless mode UNLESS fuse-overlay is configured as the mount-program. |
YES, thank you! After nuking the config and installing [storage]
driver = "overlay"
runroot = "/run/user/1000"
graphroot = "/home/andy/.local/share/containers/storage"
[storage.options]
mount_program = "/bin/fuse-overlayfs" So in all, the following will get rootless working on Arch: sudo echo "$USER:100000:65536" >> /etc/subuid
sudo echo "$USER:100000:65536" >> /etc/subgid
sudo sysctl kernel.unprivileged_userns_clone=1
sudo echo "kernel.unprivileged_userns_clone = 1" >> /etc/sysctl.d/96-userns.conf
git clone [email protected]:fuse-overlayfs-git
cd fuse-overlayfs-git
makepkg -sci That Thanks so much! |
Arch Linux
Ext4
I thought that the overlay(2) driver was pretty much always recommended, but since I upgraded buildah to 1.6, it seems to say it's not supported over extfs anymore, though I can't find info on that anywhere. Can anyone clear things up for me? I believe vfs performance is expected to be awful. What should I be using?
/etc/containers/storage.conf
:/~/.config/containers/storage.conf
:The text was updated successfully, but these errors were encountered: