Allow forcing overlayfs #2265
Description
Currently podman/buildah won't attempt to mount native overlay filesystems for images, by first probing for the backing filesystem. This is probably very reasonable in most setups, however when using sysbox as the container runtime, this leads to podman being unable to use sysbox' overlayfs support. If I understand their description correctly, they intercept syscalls and make sure the mount goes to a dynamic per-container path that is not on an overlayfs.
Sysbox' documentation on the topic: https://github.com/nestybox/sysbox/blob/46ba726e8e894aa22e20465a32d22dfa2863ec12/docs/user-guide/design.md#overlayfs-mounts-inside-the-sysbox-container
This issue came up when running podman via gitlab-ci runners using the docker executor with the sysbox runtime.
I propose 2 solutions:
- Change the storage driver to actually attempt to mount using the native overlayfs and only when that fails, fallback to fuse and eventually fail completely
- Add a configuration option to force the use of native overlay driver.