harbor-registry¶
| Field | Value |
|---|---|
| ID | harbor-registry |
| Class | host |
| Role | container-registry |
| Status | active |
| Primary IP | 192.168.6.119 |
| Proxmox | LXC 119 on prox |
| Inventory | inventory/hosts/harbor-registry.yaml |
Overview¶
Harbor container registry LXC (Ubuntu). Tagged prod in inventory — intended
for private image storage. Not deployed or configured from this monorepo.
Hardware (inventory)¶
| Resource | Value |
|---|---|
| vCPU | 8 |
| RAM | 4 GB |
| Disk | 80 GB rootfs |
Access¶
| Method | Target |
|---|---|
| SSH (operator) | ssh harbor — 1Password item harbor (root@192.168.6.119) |
| Web UI | https://192.168.6.119 (typical Harbor port 443 — verify on host) |
| Proxmox | LXC 119 console on prox |
Operator keys on root are synced from ~/.ssh/1Password/*.pub via
scripts/ops/sync-discovery-lxc-operator-keys.py.
Patch-controller key (from="192.168.6.17") is always included for infra-services automation.
DNS: Proxmox LXC 119 must use -nameserver 192.168.6.17 (AdGuard on
infra-services). Without it, the guest inherits prox
Tailscale MagicDNS (100.100.100.100), which is unreachable from the container
and breaks apt update. Verify on prox: pct config 119 | grep nameserver.
Runbooks¶
- Registry backup and upgrade procedures live on the host or Harbor docs — not yet captured in this repo.
- Proxmox API token — guest-agent investigation pattern
Related¶
- prox — hypervisor
- infra-services — primary Docker/GitOps host (no Harbor stack here today)