Mount bpffs into kind node via extraMounts#525
Closed
alebedev87 wants to merge 1 commit into
Closed
Conversation
Podman-based kind clusters do not propagate host sysfs mounts into the node container, so `/sys/fs/bpf` is not visible inside the node even when bpffs is mounted on the host. This causes the `mount-bpffs` init container to fail with "operation not permitted" because it cannot mount a new filesystem onto the isolated sysfs. Add an `extraMounts` entry to bind-mount `/sys/fs/bpf` from the host into the kind node with bidirectional propagation. This is harmless on Docker (where the mount is already visible) and fixes the init container failure on Podman. Co-Authored-By: Claude Signed-off-by: Andrey Lebedev <alebedev@redhat.com>
Contributor
Author
|
The problem of using |
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
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.
Podman-based kind clusters do not propagate host sysfs mounts into the node container, so
/sys/fs/bpfis not visible inside the node even when bpffs is mounted on the host. This causes themount-bpffsinit container to fail with "operation not permitted" because it cannot mount a new filesystem onto the isolated sysfs.Add an
extraMountsentry to bind-mount/sys/fs/bpffrom the host into the kind node with bidirectional propagation. This is harmless on Docker (where the mount is already visible) and fixes the init container failure on Podman.#490 introduced a bpffs mount done by the agent itself however on machines with
podmanbpffs mount fails withoperation not permitted: