-
Notifications
You must be signed in to change notification settings - Fork 86
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
Symlink from /etc/<dir> to /usr/etc/<dir> breaks install to-filesystem #942
Comments
It's not about the symlink, it's about having both What are you putting in (The semantics right now apparently are that we end up effectively silently "merging" the two but again, not something I want to try to support)
Hmm fun, that's a different bug where we apparently aren't setting an error correctly. |
Ref containers#942 We don't want to support this, lint against it. Signed-off-by: Colin Walters <[email protected]>
Completely unrelated to this bug, but fwiw rpm directly supports fetching URLs so the reproducer boils down to
(And if you do want to fetch URLs, |
And sorry so I now understand I (or someone) needs to go talk to the https://github.com/NERSC/podman-hpc folks about this, it's not something you specifically are doing. |
Universal blue also used to use both We found that out when building rechunk and quirked it I think its done enough where it might be warranted to quirk it and throw a warning instead. |
It was really never intended for that. Do you have references to where this hack was used so we can track them? When doing container layering in particular it's totally fine to overwrite files owned by packages, especially for |
Here are some of the PRs that fixed that hack when we switched to rechunk Currently, the only place it is used is the policy.json file due to (1) |
@rainest FYI, https://github.com/NERSC/podman-hpc/releases/tag/v1.1.1 includes a fix on their side for this. Looks like that got rolled up into the current latest in https://github.com/NERSC/podman-hpc/releases/tag/v1.1.3 |
Ours was just (2) for lack of knowledge about the separate flag for config location when prefixing the Python install 👍 Dunno if there's still reason to keep it open for the (1) case, or to just fix the error propagation. |
I've installed an RPM that includes a symlink from a path under
/etc
to a path under/usr/etc
. In the container image:Attempting to run
bootc install to-filesystem
with this image (Containerfile) fails. Using https://github.com/osbuild/bootc-image-builder, the error is:log.txt is the complete log.
This comes from ostree-ext/src/container/store.rs and ostree-ext/src/tar/write.rs AFAICT.
Building from an image without the link (Containerfile) succeeds.
This looks a bit similar to #637 and #856, but with a symlink rather than a hard link.
The text was updated successfully, but these errors were encountered: