local-registry

Manage a localhost OCI registry for Bottlerocket kits using brdev commands.

5|12|Updated Nov 24, 2025

Search Tags:#Docker #offline #registry #brdev #kit-development #local-registry #Bottlerocket

Ready to run

npx skills add https://github.com/cbgbt/bottlerocket-forest --skill local-registry

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables developers to spin up and manage a local OCI registry for Bottlerocket kits, enabling offline testing and local publishing without depending on external registries.

Core Features & Use Cases

Local registry hosting: Start a persistent registry on localhost for Bottlerocket kits.
Kit publishing and retrieval: Push and pull Bottlerocket kits to/from the local registry during grove workflows.
Use Case: When developing a new kit for a Bottlerocket variant, publish to the local registry and consume it in a test grove.

Quick Start

Start the local registry with brdev registry start Check status with brdev registry status Retrieve the registry URL with brdev registry url View live logs with brdev registry logs

Frequently Asked Questions about local-registry

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

FAQPage Schema

How do I run a local OCI registry for Bottlerocket kit development?▼

To run a local OCI registry for Bottlerocket kit development, use the command `brdev registry start` to initialize a persistent registry on localhost for pushing and pulling kits.

What is the best way to test Bottlerocket kits offline without an external registry?▼

Testing Bottlerocket kits offline requires spinning up a local OCI registry. This allows you to publish kits and fetch dependencies locally, enabling offline workflow testing across Bottlerocket variants without external dependencies.

Do I need Docker to set up a local registry for Bottlerocket kits?▼

Yes, you need Docker to set up a local registry for Bottlerocket kits. The Skill requires Docker alongside brdev registry commands to initialize, manage status, view logs, and clean registry data.

How can I check the status and view logs of my local Bottlerocket registry?▼

To check the status and view logs of your local Bottlerocket registry, use `brdev registry status` for health checks and `brdev registry logs` to retrieve live log output for troubleshooting.

Can I publish and retrieve Bottlerocket kits to a local registry during grove workflows?▼

Yes, you can publish and retrieve Bottlerocket kits to a local registry during grove workflows. The local registry enables pushing new kits and pulling dependencies for testing across different Bottlerocket variants.

How do I retrieve the URL for my local Bottlerocket registry?▼

To retrieve the URL for your local Bottlerocket registry, use the command `brdev registry url`. This provides the localhost address needed to configure clients for pushing and pulling kits.