Skip to content
Back to skills

K3d Registry

ASecurity

The k3d local-registry mirror (`localhost:5050` ↔ `registry.localhost:5000`) — why in-cluster pulls need it, what forge configures automatically, and how to fix a pre-existing cluster that ImagePullBackOffs.

  • 10 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 13, 2026
ai-agentsbashnodedocker

Security analysis

A100/100

Scanned November 13, 2026

npx -y skills add reliant-labs/forge --skill k3d-registry --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of K3d Registry?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for K3d Registry
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/reliant-labs-k3d-registry/badge)](https://www.skillsdirectory.com/skills/reliant-labs-k3d-registry)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: k3d-registry
description: The k3d local-registry mirror (`localhost:5050` ↔ `registry.localhost:5000`) — why in-cluster pulls need it, what forge configures automatically, and how to fix a pre-existing cluster that ImagePullBackOffs.
---

# k3d local-registry mirror (`localhost:5050` ↔ `registry.localhost:5000`)

`forge env deploy dev` builds and pushes images to host-side
`localhost:5050`. In-cluster pulls hit `registry.localhost:5000`. A
containerd mirror config bridges the two — without it, `docker push`
succeeds and pods `ImagePullBackOff` because `localhost:5050` doesn't
resolve from inside the node container.

Forge-managed k3d clusters get the mirror automatically:

- The project-templated `deploy/k3d.yaml` carries the mirrors inline
  (`registries.config` block of the k3d Simple config).
- The fallback `forge env deploy dev` create path (no `deploy/k3d.yaml`)
  writes a temp `registries.yaml` and passes `--registry-config` to
  `k3d cluster create`.

**Pre-existing k3d cluster mirror fix.** If your cluster pre-dates this
behavior — `forge env deploy dev` reuses the existing cluster, and pulls
fail with `localhost:5050: connection refused` from inside the node —
add the mirror to the running node container directly:

```bash
# Replace `k3d-dev-server-0` with your cluster's server node name
# (`docker ps --filter name=k3d`).
docker exec k3d-dev-server-0 sh -c 'cat > /etc/rancher/k3s/registries.yaml <<EOF
mirrors:
  "registry.localhost:5000":
    endpoint:
      - http://registry.localhost:5000
  "registry.localhost:5050":
    endpoint:
      - http://registry.localhost:5000
  "localhost:5050":
    endpoint:
      - http://registry.localhost:5000
EOF
'
docker restart k3d-dev-server-0
```

Or, simpler: `k3d cluster delete dev && forge env deploy dev` recreates
the cluster with the mirror in place.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.