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
Remove devicemapper storage driver #8019
base: main
Are you sure you want to change the base?
Conversation
We can use relative paths now. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
To add some context here, we were not able to remove DM earlier because it was used by Kata (see #7003 (comment)). This is no longer true (see containers/storage#1622 (comment)). As for "let's deprecate it first, when remove it" concern (see #7002 (comment)) -- I think there are no existing users. |
/test ci-cgroupv2-e2e |
The comment being removed is wrong (gosec) and redundant. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
/retest |
I vote we mark as deprecated in 1.30 and remove in 1.31, just to be safe. WDYT? |
Let's loop in kata folks. I think they were using it in some scenarios. |
Right, we had a dependency here, but it's been removed. |
/approve Please remove the hold once everyone is OK to move forward. /hold |
Looks like we have no consensus yet. |
@cri-o/cri-o-maintainers, it's been a while. Any thoughts on moving forward here? |
yeah if a user wants to use devicemapper, they can compile on their own still (until c/storage removes it) WDYT @cri-o/cri-o-maintainers |
@haircommander, sounds good! /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: haircommander, kolyshkin, kwilczynski The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind deprecation
What this PR does / why we need it:
Device mapper storage driver is hard to set up, slow, and obsoleted by overlayfs.
My best guess is nobody is using it nowadays.
Let's remove it.
Which issue(s) this PR fixes:
Fixes: #7002
Special notes for your reviewer:
Does this PR introduce a user-facing change?