Add /usr/lib/modules as a new volume to enable loading of kernel modules #78
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
It is recommended to create bricks on top of LVM (with thin-pool provisioning). This requires certain device-mapper features in the kernel. If these are missing, the lvm-tools will try to load the appropriate kernel modules. Loading of kernel modules is only possible if the .ko files are available inside the container. Fixes: gluster#75 Related: gluster/gluster-kubernetes#457 Signed-off-by: Niels de Vos <ndevos@redhat.com>
Author
|
Could you review this, @jarrpa? |
jarrpa
approved these changes
Jun 28, 2018
jarrpa
left a comment
jarrpa
left a comment
There was a problem hiding this comment.
LGTM. Does this mean we wouldn't need to specify the volume mount in a Pod spec?
nixpanic
changed the title
Author
|
That needs to be specified for all I know. But the specs (or examples) are not part of this repo. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It is recommended to create bricks on top of LVM (with thin-pool
provisioning). This requires certain device-mapper features in the
kernel. If these are missing, the lvm-tools will try to load the
appropriate kernel modules. Loading of kernel modules is only possible
if the .ko files are available inside the container.
Fixes: #75
Related: gluster/gluster-kubernetes#457
Signed-off-by: Niels de Vos ndevos@redhat.com