cli-local-build

Compile the Kurtosis CLI from source and test against Docker and Kubernetes engines.

547|97|Updated Feb 14, 2023
One-click install
npx skills add https://github.com/kurtosis-tech/kurtosis --skill cli-local-build
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cli-local-build
Source: https://github.com/kurtosis-tech/kurtosis/tree/main/skills/cli-local-build
Command: npx skills add https://github.com/kurtosis-tech/kurtosis --skill cli-local-build

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Build and test Kurtosis CLI from source to streamline development, allowing you to compile locally, run against engines, and iterate without releases.

Core Features & Use Cases

  • Local compilation and testing of the Kurtosis CLI to validate changes quickly.
  • Seamless engine interactions (start/stop, run package) for hands-on development and debugging.
  • Supports switching between Docker and Kubernetes backends to validate cross-environment behavior.

Quick Start

Compile the CLI from source and verify the version to ensure a working local build.

Frequently Asked Questions about cli-local-build

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build the Kurtosis CLI from source for local development?

Build the Kurtosis CLI locally by compiling the Go source code using the Go 1.23+ toolchain, then verify the resulting binary by checking its version to ensure a working local build.

What is the process for testing a local CLI build against Docker and Kubernetes engines?

Testing a local build involves starting the engine and running packages to validate behavior. You can switch between Docker and Kubernetes backends to verify cross-environment functionality directly.

Do I need Go installed to compile and test the Kurtosis CLI locally?

Yes, you need Go 1.23 or higher installed. Satisfying this Go tooling requirement is necessary to compile the CLI binaries and execute local development workflows.

Why compile the Kurtosis CLI locally instead of using a released version?

Compiling locally streamlines development by allowing you to iterate on CLI changes quickly, validate behavior against engines, and debug hands-on without waiting for official releases.

Can I validate CLI changes across different container engines during local development?

Yes, local development supports switching between Docker and Kubernetes backends. This allows you to validate cross-environment behavior by starting and stopping engines during your testing workflow.

What engine interactions are available when testing a local Kurtosis CLI build?

Available engine interactions include engine start and stop, cluster switching, and package execution. These commands allow hands-on development and debugging against the compiled binary.