acoustic-carpenter-78188
04/23/2026, 7:38 PMdocker-registry in the devbox used an emptyDir volume for /var/lib/registry. Every time the devbox container restarted, all pushed images were wiped and users had to rebuild and re-push their images. This is a significant friction point in the local dev loop.
What changes were proposed in this pull request?
Back the registry with a hostPath-based PVC at /var/lib/flyte/storage/registry, which sits under the VOLUME /var/lib/flyte/storage declared in the devbox Dockerfile and therefore persists across container restarts — the same pattern already used by rustfs and embedded-postgres.
• `charts/flyte-devbox/values.yaml`: enable docker-registry.persistence with existingClaim: flyte-devbox-registry-storage.
• `charts/flyte-devbox/templates/_helpers.tpl`: add flyte-devbox.persistence.registryVolumeName helper.
• `charts/flyte-devbox/templates/storage/registry/{pv,pvc}.yaml`: new hostPath PV + PVC (10Gi, manual storage class) at /var/lib/flyte/storage/registry.
• `docker/devbox-bundled/manifests/{dev,complete}.yaml`: regenerated — registry Deployment now mounts the PVC instead of emptyDir, and the new PV/PVC resources are included.
How was this patch tested?
Built the devbox image, pushed an image to the local registry, restarted the devbox container, and verified the previously pushed image was still present (no rebuild needed). Also confirmed the rendered manifests match make -C docker/devbox-bundled manifests.
Labels
fixed
Check all the applicable boxes
• I updated the documentation accordingly.
• All new and existing tests passed.
• All commits are signed-off.
• main
• #6583
• fix: persist devbox local docker registry across restarts 👈
flyteorg/flyte