Build cache
View and clean up the pip and apt package proxy state and the registry layer cache
Required permission: Global admin
Publishing variants and building serving images downloads packages and layers every time. On the build cache screen you view and clean up the two layers that reduce those downloads.
| Layer | What | If empty or unavailable |
|---|---|---|
| Package proxy (패키지 프록시) | Proxies that keep pip (proxpi) and apt (apt-cacher-ng) downloads | Not used (미사용) (not configured) is normal — builds download directly from the internet. Failed (실패) (configured but not responding) means builds that use that proxy cannot fetch packages and fail. The proxy is not a mirror, so there is no fallback to the internet |
| Layer cache (레이어 캐시) | {tenant}/cache/… repositories inside the built-in registry. They are not images, so they do not appear on the container registry screen. There is one card per tenant, and the cache from building shared images appears on the "Shared (mlops) (공유 (mlops))" card | The next build starts from scratch (it only takes longer) |
Clean up the package proxies
Each proxy card shows its state (Healthy (정상) / Warning (주의) / Failed (실패) / Not used (미사용)), address, and which builds it is injected into (pip: training runtime, dataset stager and serving builder; apt: training runtime and serving builder). The cleanup buttons below ask for confirmation and are locked while the proxy is Failed (실패). Refresh (다시 확인) at the top reloads the state.
- Invalidate index cache (인덱스 캐시 무효화) on the pip proxy — discards only the PyPI index cache. Downloaded wheel files stay, and proxpi manages them. Use it when a newly released package version is not visible to builds.
- Run expiry cleanup (만료 정리 실행) on the apt proxy — cleans up files that the indexes no longer point to. It marks them first and deletes them in the next cycle.
Clean up the layer cache — two steps
Deleting a repository and getting disk space back are different things. Within a tenant, a layer can be pointed to by both an image and the cache, so deleting a cache repository frees no disk space for layers an image still uses.
- In the repository table on the tenant card, press Delete (삭제) on cache repositories you no longer need to delete them. "Referenced size (참조 용량)" in the table is how much that repository points to, not how much will be reclaimed.
- If "Reclaimable N (M items) (회수 가능 N (M개))" appears under the card title, press Reclaim (회수) on the right. It deletes only orphaned layers that no manifest points to, and gets real disk space back.