-
Notifications
You must be signed in to change notification settings - Fork 247
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
Podman v4.3.1 to 4.4.4 introduced breaking change for unsupported filesystems #1546
Comments
The operating environment is WSL1 Alpine Linux 3.17 with /var/lib/containers on WSLFS. Similar issues suggest Due to some concerns with running without systemd, PROPAGATION was set to shared, but likely was unnecessary.
Working v4.3.1 podman info:
|
I think the issue is caused by d9da335. I am fine with reverting the change, I am usually against these overzealous checks that block valid use cases. |
The overlay driver previously raised an error when encountering an unsupported filesystem. This commit changes the error message to a debug log, allowing the overlay driver to continue its operation even with unsupported filesystems, without causing a failure. [NO NEW TESTS NEEDED] Introduced-by: containers#1374 Closes: containers#1546 Signed-off-by: Giuseppe Scrivano <[email protected]>
opened a PR: #1547 |
b
Hi Giuseppe, If I understand correctly, since the backing filesystem is not supported with OverlayFS it would not be safe to continue. |
@aarontomlin I'm running on WSL1 which doesn't support overlayfs, yet skopeo, podman, and buildah previously were all able to work with copying, syncing, inspecting, building images. With the change in these new versions, that capability is broken. I'm not sure if filesystem type 0x53464846 aka WSLFS should be whitelisted, or if the diagnosis should be a soft error. At the very least, for my use case a flag to allow the check to be ignored would let the tools be functional. |
… not supported with OverlayFS" This reverts commit d9da335. Closes: containers#1546 Signed-off-by: Giuseppe Scrivano <[email protected]>
Issue Description
On 4.3.1 and earlier, unsupported filesystems, such as
0x53464846
for WSLFS would not abort the command and would complete the action.Steps to reproduce the issue
Steps to reproduce the issue
Describe the results you received
Describe the results you expected
podman info output
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
Yes
Additional environment details
Running as root on WSL1 alpine linux.
Additional information
Issue seems related to this pull request:
Update c/storage after #1436
As the issue affects the latest versions of buildah and skopeo, suggesting a change in error handling in c/images is impacting all 3 products. A possible fix would be to add type 0x53464846 as "WSLFS" as a supported filesystem to bypass the error handling.
The text was updated successfully, but these errors were encountered: