Skip to content

rechunker: Do cleanup too #5307

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.

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

Open
cgwalters opened this issue Feb 25, 2025 · 0 comments
Open

rechunker: Do cleanup too #5307

cgwalters opened this issue Feb 25, 2025 · 0 comments
Labels
area/build-chunked Issues related to chunked image builds

Comments

@cgwalters
Copy link
Member

It'd be quite useful if we scope-creeped the rechunker into general "image cleanup"/analyzer.

Especially I think it'd be nicer to fix things like bootc-dev/bootc#1096 at build time - and we have the power to do that here.

Related to all of this is: Today the rechunking code is kind of carefully written to not mutate the input root filesystem. It'd actually be way less awkward if we did do that, because then we could e.g. blow away /sysroot etc instead of just trying to avoid committing it.

I think the reason I may have written things this way is I thought that RUN --mount=type=bind,from=<somageimage>,target/someimage was always read only but it's totally supported to pass rw to get a temporary overlayfs...and there's no good reason not to just require that really.

@cgwalters cgwalters added the area/build-chunked Issues related to chunked image builds label Feb 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/build-chunked Issues related to chunked image builds
Projects
None yet
Development

No branches or pull requests

1 participant