Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Allow pre-populate buildpack cache #380

Open
viceice opened this issue May 9, 2022 · 0 comments
Open

Allow pre-populate buildpack cache #380

viceice opened this issue May 9, 2022 · 0 comments
Labels
priority-3-normal Default priority, "should be done" but isn't prioritised ahead of others status:ready Ready to start implementation type:feature Feature (new functionality)

Comments

@viceice
Copy link
Member

viceice commented May 9, 2022

We should provide a new tool to pre-populate the buildpack cache, so users can easily pre-download those files (including the required hashes)

Use-Case:

Some users are running the full docker image because or air-gaped systems. So when we change the full image to binarySource=install, it will break those users.
@viceice viceice added type:feature Feature (new functionality) priority-3-normal Default priority, "should be done" but isn't prioritised ahead of others status:ready Ready to start implementation labels May 9, 2022
@viceice viceice changed the title Allow prepoppulate buildpack cache Allow pre-populate buildpack cache May 9, 2022
@viceice viceice mentioned this issue Jan 30, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority-3-normal Default priority, "should be done" but isn't prioritised ahead of others status:ready Ready to start implementation type:feature Feature (new functionality)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@viceice