build-kit-locally

Build Bottlerocket kits and publish them to a local OCI registry.

5|12|Updated Nov 24, 2025

Search Tags:#automation #docker #publish #kit-build #local-registry #development-testing #Bottlerocket

Ready to run

npx skills add https://github.com/cbgbt/bottlerocket-forest --skill build-kit-locally

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: build-kit-locally
Source: https://github.com/cbgbt/bottlerocket-forest/tree/main/skills/build-kit-locally
Command: npx skills add https://github.com/cbgbt/bottlerocket-forest --skill build-kit-locally

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of building Bottlerocket kits (core-kit or kernel-kit) and publishing them to a local OCI registry for development testing, enabling quick validation without touching production registries.

Core Features & Use Cases

Local kit build: compile the kit in your grove and prepare it for publishing.
Local publish: push built kits to a local registry for testing with dependent images.
Use Case: When modifying a kit, run builds and publish to local registry to validate variant images before integration.

Quick Start

Ensure the local registry is running: brdev registry start
Configure for local publishing: cd kits/<kit-name>; brdev twoliter use-local-publish
Build the kit: make build (optionally ARCH=x86_64 or ARCH=aarch64)
Publish to local registry: make publish VENDOR=local
Verify: brdev registry list

Frequently Asked Questions about build-kit-locally

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

FAQPage Schema

How do I build Bottlerocket kits and publish them to a local registry for testing?▼

To build Bottlerocket kits and publish them to a local registry, start the local registry using brdev, configure the kit with brdev twoliter use-local-publish, run make build, and execute make publish VENDOR=local.

What dependencies do I need to build and publish Bottlerocket kits locally?▼

You need Docker, a kit repository under the kits/ directory, and Brdev tooling to configure and publish Bottlerocket kits to your local OCI registry for development testing.

Can I specify a target architecture when building Bottlerocket kits locally?▼

Yes, you can specify a target architecture when building Bottlerocket kits by passing the ARCH variable to the build command, using make build ARCH=x86_64 or make build ARCH=aarch64.

How do I verify that a Bottlerocket kit was successfully published to my local registry?▼

To verify that your Bottlerocket kit was successfully published to the local registry, run the command brdev registry list to check the published images.

When should I publish Bottlerocket kits to a local OCI registry instead of a production registry?▼

You should publish Bottlerocket kits to a local OCI registry when you modify a kit and need quick variant testing within a dedicated grove to validate dependent images before integration.

What Bottlerocket kit types can I build and publish using this local registry workflow?▼

You can build and publish core-kit or kernel-kit variants to your local registry, allowing you to validate modified kit images locally before pushing to production.