-
Notifications
You must be signed in to change notification settings - Fork 251
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
Allow forcing overlayfs #2265
Comments
this can easily be reproduced:
|
why does the check for overlay fails when running inside sysbox? |
@giuseppe it doesn't. The problem isn't that the check doesn't work, but that it shouldn't be done in the first place. Sysbox uses native overlayfs and so podman detects that and immediately falls back to alternatives. However: Sysbox intercepts the mount operation to work regardless: https://github.com/nestybox/sysbox/blob/master/docs/user-guide/design.md#overlayfs-mounts-inside-the-sysbox-container, at least that's what they claim. |
could you please share the output of |
Weirdly I don't think this is the same behavior I had when I reported this issue, not sure what changed in the meantime. But it fails non the less. |
the podman image has some preconfigured settings in |
Can you provide some examples? |
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:
The text was updated successfully, but these errors were encountered: