Quickstart

Early access. Registry is rolling out behind an organization flag. If the commands below report that the registry surface is unavailable, ask us to enable it for your organization.

You’ll need: the lbr CLI (logged in with lbr login), Docker, and an active payment method on your organization.

1. Create a registry

The slug is globally unique and becomes the first path segment of every image.

lbr registry create acme-prod --display-name "Acme production"

2. Log in

lbr registry login wires Docker to fetch a fresh, short-lived credential for every pull and push — nothing long-lived is written to disk. One login covers every registry in your organization.

lbr registry login

This points Docker’s credential store at lbr for registry.lngbrdg.com. Add --registry acme-prod to scope the session to one registry, or --pull for read-only. To push from CI instead, mint a key (lbr registry key mint …) or set up a keyless OIDC rule.

3. Push an image

Tag any image under your registry’s path and push it.

docker pull alpine:3.20
docker tag alpine:3.20 registry.lngbrdg.com/acme-prod/alpine:3.20
docker push registry.lngbrdg.com/acme-prod/alpine:3.20

4. Pull it back

docker pull registry.lngbrdg.com/acme-prod/alpine:3.20

5. Pull a public image through the cache

Prefix any catalog upstream with <registry>/cache/ to pull it through your registry — cached after the first fetch, and served from the EU on the next.

docker pull registry.lngbrdg.com/acme-prod/cache/docker.io/library/redis:7

Where to next

• Pushing and pulling — the full workflow, including oras and multi-arch images.
• Registry keys — long-lived credentials for CI and services.
• Core concepts — the mental model behind all of it.