Skip to content
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

Detect when the VFS graph driver is used #1011

Open
almet opened this issue Nov 26, 2024 · 2 comments
Open

Detect when the VFS graph driver is used #1011

almet opened this issue Nov 26, 2024 · 2 comments
Labels
container enhancement New feature or request good first issue Good for newcomers

Comments

@almet
Copy link
Contributor

almet commented Nov 26, 2024

We've had issues opened on the repository where users are using the VFS storage driver (#993).

This driver is not meant to be used in production, and makes dangerzone fail. We should detect it is used and report it to the end user.

@almet
Copy link
Contributor Author

almet commented Nov 26, 2024

vfs seem to be the default podman storage backend on debian bookworm, from what I understand.

Installing the containers-storage package seem to change the default backend to overlayfs2 so we might want to point this out.

@apyrgio
Copy link
Contributor

apyrgio commented Nov 28, 2024

I suppose you propose adding a runtime check for the vfs driver, right, perhaps as part of the instalation? I'd be in favor of that. What about suggesting a solution to our users. On Windows/macOS, it seems the issue was resolved once users reinstalled Docker Desktop. On Linux, we could ask them to create a .config/containers/storage.conf file with the proper driver. What do you think?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
container enhancement New feature or request good first issue Good for newcomers
Projects
Status: Todo
Development

No branches or pull requests

2 participants