Skip to content

Conversation

yuvipanda
Copy link
Contributor

As part of jupyterhub/binderhub#1941, I want to not port imageCleaner to the new chart. Since the image store is not really used to push anymore (since jupyterhub/repo2docker#1421) and we will be able to disregard it completely in the future, we can simply just prune the entire image store than do any complex logic here.

As part of jupyterhub/binderhub#1941,
I want to not port imageCleaner to the new chart. Since the
image store is not really used to push anymore (since
jupyterhub/repo2docker#1421) and we will
be able to disregard it completely in the future, we can simply
just prune the entire image store than do any complex logic here.
@yuvipanda yuvipanda merged commit dc30afa into jupyterhub:main Mar 8, 2025
8 checks passed
@manics
Copy link
Member

manics commented Mar 10, 2025

Cronjobs only run on one node at a time- are we sure they'll be randomly scheduled across all build nodes at a frequent enough interval?

yuvipanda added a commit to yuvipanda/mybinder.org-deploy that referenced this pull request Mar 10, 2025
This is practically a no-op, but we want imageCleaner enabled
still on multi-node instances

See jupyterhub#3249 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants