Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

lxc: Unknown capability perfmon #35

Open
r10r opened this issue Feb 3, 2021 · 0 comments
Open

lxc: Unknown capability perfmon #35

r10r opened this issue Feb 3, 2021 · 0 comments
Assignees

Comments

@r10r
Copy link
Contributor

r10r commented Feb 3, 2021

Deploying cilium fails with

ERROR conf - conf.c:dropcaps_except:2451 - Unknown capability perfmon

Workaround

Disable capabilities support by settingCRIO_LXC_CAPABILITIES=false in /etc/default/crio-lxc

Problem

Cri-o requests capablities that are unknown to the installed liblxc version.
Commit lxc/lxc@7b4cd46 added capabilities support for new capabilities introduced by linux 5.8 CAP_BPF and CAP_PERFMON. The forked liblxc version is not recent enough and must be upgraded.

Detailed Description

Capabilities are set by cri-o. For privileged containers e.g cilium all supported capabilities are set.
cri-o uses the library github.com/syndtr/gocapability to list all supported capabilities.

The gocapability library was updated in syndtr/gocapability#17 to support CAP_BPF and CAP_PERFMON.

cri-o then upgraded the gocapability dependency in cri-o/cri-o#4462

-       github.com/syndtr/gocapability v0.0.0-20180916011248-d98352740cb2
+       github.com/syndtr/gocapability v0.0.0-20200815063812-42c35b437635

Conclusion

  • Track whether new capabilities are introduced when changing the kernel version.
  • Ensure that the liblxc version is recent enough for the underlying kernel and supports all available capabilities.
@r10r r10r self-assigned this Feb 3, 2021
@r10r r10r changed the title lxc: conf - conf.c:dropcaps_except:2451 - Unknown capability perfmon lxc: Unknown capability perfmon Feb 3, 2021
@r10r r10r transferred this issue from another repository Mar 24, 2021
@r10r r10r transferred this issue from another repository Apr 8, 2021
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Development

No branches or pull requests

1 participant