-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Remove device mapper storage driver support #7003
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
Conversation
We can use relative paths now. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kolyshkin 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 |
OK, this is blocked by buildah which can't be built without libdevmapper. Moving to draft until we have buildah release with containers/buildah#4832 included |
PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@kolyshkin: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
@kolyshkin, devmapper can be used with Kata Containers and in the Confidential Containers front it'll be heavily used. We're using devmapper as TEE capable kernels do not support virtio-fs, virtio-9p is not supported by several distros (and also by several hypervisors), leaving us with the only option to use devmapper as the way to share the container rootfs between host and guest via a block device. I know, Red Hat OpenShift is not using it, AFAIU, but other users of CRi-O could. This is not a show stopper for this PR, but I'd love to have it taken into consideration. /cc @littlejawa @bpradipt |
@fidencio: GitHub didn't allow me to request PR reviews from the following users: bpradipt. Note that only cri-o members and repo collaborators can review this PR, and authors cannot review their own PRs. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
A friendly reminder that this PR had no activity for 30 days. |
This fix has been included in https://github.com/containers/buildah/releases/tag/v1.31.0 |
A friendly reminder that this PR had no activity for 30 days. |
Closing this PR since it had no activity in the past 90 days. |
Resurrected as #8019 |
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?