This guide explains how to configure BoxLite to pull OCI container images from custom registries, such as a private enterprise registry, a third-party registry like ghcr.io or quay.io, or a local caching proxy.
When you ask BoxLite to create a box from an image (e.g., image="alpine"), it needs to resolve this "unqualified" reference into a full image reference (e.g., docker.io/library/alpine:latest).
By default, if no registries are configured, BoxLite uses docker.io (Docker Hub) as the implicit default.
You can provide a list of custom registries. BoxLite will try to pull the image from each registry in the provided order. The first successful pull wins. If all registries fail, the operation returns an error.
Fully qualified image references (e.g., quay.io/prometheus/prometheus:v2.40.1) always bypass this search mechanism and are pulled directly.
The CLI layers configuration sources with the following priority (from lowest to highest):
- Default:
docker.io - Configuration File (
--config): Loads configuration from the specified path - CLI Flags (
--registry): Prepended to registries from config file (highest priority)
Create a JSON configuration file with your registry preferences:
{
"image_registries": [
"ghcr.io",
"quay.io",
"docker.io"
]
}image_registries(optional): List of registries to search for unqualified image references.
Use the --config flag to specify your configuration file:
# Use a project-specific configuration
boxlite --config ./project-config.json run alpineImportant: If you specify a config file with --config and the file does not exist or is invalid, the command will fail with an error.
You can use the global --registry flag with boxlite run or boxlite create. You can specify it multiple times.
These flags are prepended to your configured list. This allows you to force a specific registry to be checked first for a single command without editing your config file.
# Assume config.json contains ["ghcr.io", "docker.io"]
# This command will search:
# 1. my.private.registry.com (from flag)
# 2. ghcr.io (from config)
# 3. docker.io (from config)
boxlite --config ./config.json \
run --registry my.private.registry.com \
my-internal-app:latestThe SDKs are "pure" by design. They do not automatically load any configuration file. This ensures that your code's behavior is deterministic and doesn't silently depend on the user's local environment.
- Programmatic Options: You explicitly pass the list of registries when initializing the runtime.
- Default:
docker.io(if you pass an empty list or nothing).
Pass image_registries to boxlite.Options.
import boxlite
# Configure a runtime to search ghcr.io first, then docker.io
options = boxlite.Options(
image_registries=["ghcr.io", "docker.io"]
)
runtime = boxlite.Boxlite(options)
# When creating a box, 'alpine' will be tried as:
# 1. ghcr.io/library/alpine
# 2. docker.io/library/alpine
async with boxlite.SimpleBox(image="alpine", runtime=runtime) as box:
await box.exec(["echo", "Hello!"])Pass imageRegistries to the JsBoxlite constructor.
import { JsBoxlite, SimpleBox } from '@boxlite-ai/boxlite';
// Configure a runtime to search ghcr.io first, then docker.io
const runtime = new JsBoxlite({
imageRegistries: ['ghcr.io', 'docker.io']
});
// Pass the custom runtime to the box constructor
const box = new SimpleBox({
image: 'alpine',
runtime: runtime
});
await box.exec('echo', 'Hello!');If you want your SDK application to respect a configuration file, you can manually load it. This puts the control in your hands.
import boxlite
import json
from pathlib import Path
def load_boxlite_options(config_path: str):
"""Load BoxLite options from a configuration file."""
with open(config_path) as f:
config = json.load(f)
return boxlite.Options(
image_registries=config.get("image_registries", [])
)
# Use it
runtime = boxlite.Boxlite(load_boxlite_options("./config.json"))