The College of Letters & Science IT (CIT)
SSMS | Life Sciences | Santa Barbara, CA 93106-4020
cit.ucsb.edu
Every time you launch a project on L&S Cloud BinderHub, a container image is built from your repository's configuration files (requirements.txt, environment.yml, Dockerfile, APT.txt) and stored in CIT's internal container registry. This page explains how images are cached, reused, and retired over time.
When you submit a repository URL to BinderHub, the following occurs:
| Policy | Details |
|---|---|
| Cache Retention Window | TODO: confirm with CIT |
| Garbage Collection Trigger | TODO: confirm with CIT |
| Impact of Expiration | Expired images are removed from the registry. Subsequent launches of the same commit trigger a rebuild (a one-time delay, not data loss). |
| Manual Deletion by Users | TODO: confirm with CIT |
Note: Image expiration from the registry does not affect your code or data. The git repository remains the source of truth — expired images are simply rebuilt on next launch as described above.
If a cached image has expired and you notice a longer-than-usual build time, follow these steps:
https://binder.college.ucsb.edu and enter your repository URL as normal.Questions about retention windows, registry storage limits, or early image removal should be directed to CIT Support - Get Help.