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

RFC: remove devmapper driver #1619

Closed
kolyshkin opened this issue May 24, 2023 · 5 comments · Fixed by #1622
Closed

RFC: remove devmapper driver #1619

kolyshkin opened this issue May 24, 2023 · 5 comments · Fixed by #1622

Comments

@kolyshkin
Copy link
Contributor

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.

@rhatdan
Copy link
Member

rhatdan commented May 26, 2023

Makes sense to me.
@nalind @rhvgoyal @vrothberg @giuseppe @mtrmac @saschagrunert WDYT?

@giuseppe
Copy link
Member

yes, I agree, let's drop old unmaintained stuff

@saschagrunert
Copy link
Member

saschagrunert commented May 30, 2023

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.

@alicefr
Copy link
Contributor

alicefr commented May 30, 2023

@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.

@vrothberg
Copy link
Member

SGTM 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants