Caching support for inner image?

Every time I launch a new workspace with envbox, and it's downloading the huge image for development environment, which takes times and consume unnecessary bandwidth. Without envbox the k8s serve the image from cache resulting in faster new workspace launch.

Start by tracing how envbox launches the inner development image in Kubernetes and review the repository's related image-handling entry points. Confirm the desired caching behavior and test that a new workspace can reuse the cached image without downloading it again.

Scritto dal modello di indicizzazione a partire dal testo della issue.