-
-
Notifications
You must be signed in to change notification settings - Fork 104
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
feat(libbpf/bpftool): scaffold libbpf/bpftool #28494
Conversation
Not sure how i have to do the test. |
https://aquaproj.github.io/docs/products/aqua-registry/contributing/#how-to-add-a-package
You can also execute tools in a container by $ cmdx con
+ bash scripts/connect.sh
[INFO] Connecting to the container aqua-registry (linux/arm64)
root@9238446e53ff:/workspace# bpftool --help
Usage: bpftool [OPTIONS] OBJECT { COMMAND | help }
bpftool batch file FILE
bpftool version
OBJECT := { prog | map | link | cgroup | perf | net | feature | btf | gen | struct_ops | iter }
OPTIONS := { {-j|--json} [{-p|--pretty}] | {-d|--debug} |
{-V|--version} } If you want to run tools in your machine without containers, there are two ways.
packages:
# ...
- import: pkgs/libbpf/bpftool/pkg.yaml You need to run aqua policy allow Then you can run bpftool. bpftool --help
export AQUA_GLOBAL_CONFIG=$PWD/aqua-all.yaml:$AQUA_GLOBAL_CONFIG You need to run aqua policy allow Then you can run all tools. bpftool --help
aqua makes commands executable. |
I'll update the document. |
v4.247.0 is out 🎉 |
libbpf/bpftool: Automated upstream mirror for bpftool stand-alone build
Check List
Require signed commits
, so all commits must be signed