summaryrefslogtreecommitdiffstats
path: root/recipes-containers/containerd/containerd-opencontainers/0001-Makefile-allow-GO_BUILD_FLAGS-to-be-externally-speci.patch
diff options
context:
space:
mode:
authorKoen Kooi <koen.kooi@oss.qualcomm.com>2026-04-17 09:31:34 +0200
committerBruce Ashfield <bruce.ashfield@gmail.com>2026-04-21 02:30:58 +0000
commit115184e6c9dbca661c3359f039f88faa76a72b4f (patch)
tree048e0e162f5a15d918b4a0b419bf6baa0f0b0ecb /recipes-containers/containerd/containerd-opencontainers/0001-Makefile-allow-GO_BUILD_FLAGS-to-be-externally-speci.patch
parentc83f423bfed7963d2f98276f8cd5d13f2cfda4ca (diff)
downloadmeta-virtualization-master.tar.gz
cdi: add container-device-interface commandline utilityHEADmaster
From the upstream description: The `cdi` command-line tool is a utility for inspecting and interacting with the CDI (Container Device Interface) cache. It allows developers and system administrators to: - List CDI Spec files: View all available CDI specification files in the configured directories - List vendors: Display registered device vendors in the CDI cache - List device classes: Show available device classes from CDI Specs - List devices: Enumerate all CDI devices available in the system - Validate specs: Verify CDI specification files against the JSON schema - Inject devices: Inject CDI device configurations into OCI runtime specifications - Monitor cache: Watch for changes in the CDI cache and Spec directories - Resolve devices: Resolve fully-qualified device names to their configurations The CLI tool is particularly useful for debugging CDI configurations, validating spec files, and testing device assignments before deploying them in production environments. Signed-off-by: Koen Kooi <koen.kooi@oss.qualcomm.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Diffstat (limited to 'recipes-containers/containerd/containerd-opencontainers/0001-Makefile-allow-GO_BUILD_FLAGS-to-be-externally-speci.patch')
0 files changed, 0 insertions, 0 deletions