-
Notifications
You must be signed in to change notification settings - Fork 246
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
RFC: remove devmapper driver #1619
Comments
Makes sense to me. |
yes, I agree, let's drop old unmaintained stuff |
I agree we should remove it if nobody maintains it any more. @alicefr are you aware of anyone using devicemapper? I'm not sure if we discussed something like this in the past. |
@saschagrunert not that I'm aware. AFAIU, kata is relying on virtiofs, hence a filesystem storage driver will be enough. I still believe that for confidential computing use cases, we will need some block-based storage drivers, but probably not devicemapper. |
SGTM 👍 |
It seems that no one is using devicemapper storage driver nowadays, since overlayfs is so much better.
Can it be deprecated and removed? I see that moby/moby did that recently.
The text was updated successfully, but these errors were encountered: