docker-local-build

Builds and tests Kurtosis from source on local Docker, compiling Engine, Core, Files Artifacts Expander, CLI, tagging images with git short SHA, and restarting the engine for a clean test environment.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Build and test Kurtosis from source on local Docker.

Core Features & Use Cases

  • End-to-end local build: compile Engine, Core (APIC), and Files Artifacts Expander, plus the CLI binary.
  • Version tagging & consistency: images are tagged with the git short SHA (plus -dirty if needed) and the same tag is embedded into the CLI as KurtosisVersion.
  • Engine reset & quick validation: after building, the workflow restarts the engine to provide a clean test environment.

Quick Start

Use the local-build script from the repo root to perform a full build, install the CLI, and reset the engine.

Frequently Asked Questions about docker-local-build

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

FAQPage Schema
How do I build Kurtosis from source locally using Docker?▼

To build Kurtosis from source locally, run the local-build script from the repo root to compile Engine, Core, and Files Artifacts Expander, build Docker images, install the CLI, and restart the engine for a clean test environment.

What prerequisites do I need to compile Kurtosis locally?▼

Compiling Kurtosis locally requires Go 1.23+, Docker, and docker buildx installed in your development environment to handle the end-to-end build process and image creation.

How does the local Docker build tag images and versions?▼

The local Docker build tags images with the current git short SHA, appending a -dirty suffix for uncommitted changes, and embeds the same tag into the CLI binary as the KurtosisVersion.

Does the local build process reset the Kurtosis engine automatically?▼

Yes, after building and installing the CLI, the workflow restarts the Kurtosis engine to provide a clean test environment for development and validation.

Why does my local Kurtosis Docker image have a -dirty tag?▼

A -dirty tag suffix appears when there are uncommitted changes in your local git repository during the Docker image build process, distinguishing it from clean commit builds.

Can I use this local build workflow to test Kurtosis Core and CLI changes?▼

Yes, the workflow compiles Kurtosis Core (APIC) and the CLI binary from source, embedding the git short SHA as KurtosisVersion to ensure version consistency during local testing.