-
Notifications
You must be signed in to change notification settings - Fork 74
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
bootc switch error: ostree-tar: Processing deferred hardlink #637
Comments
Except...
is an important thing here to be able to reproduce and we're missing that. Please either:
(Or of course both!) |
Prior issues/PRs in this area are:
Based on the symptoms, it might be that something in your script is doing e.g.
If so, it may be a workaround to first copy the file via e.g.
or so |
I hit this, or something very similar while building a qcow2 image from a bootc container To reproduce, create a container with the following Containerfile:
And then try to generate an image out of it:
It fails with:
|
ostreedev/ostree-rs-ext#648 fixes this. |
This (not tested locally) change should work around containers/bootc#637 It's all tricky because you'll only again see this when using the `vfs` backend. The `overlay` backend always breaks hardlinks. For more, see e.g. ostreedev/ostree-rs-ext#408 Signed-off-by: Colin Walters <[email protected]>
Fixed by #666 |
This (not tested locally) change should work around containers/bootc#637 It's all tricky because you'll only again see this when using the `vfs` backend. The `overlay` backend always breaks hardlinks. For more, see e.g. ostreedev/ostree-rs-ext#408 Signed-off-by: Colin Walters <[email protected]>
This (not tested locally) change should work around containers/bootc#637 It's all tricky because you'll only again see this when using the `vfs` backend. The `overlay` backend always breaks hardlinks. For more, see e.g. ostreedev/ostree-rs-ext#408 Signed-off-by: Colin Walters <[email protected]>
The Containerfile looks like:
Being BASE_IMAGE the bootc RHEL 9.4 image.
The text was updated successfully, but these errors were encountered: