Kseems odd
Ai put it on the releases as a warning
Aof rechunk
FWhen trying to do
https://github.com/fiftydinar/gidro-os/actions/runs/10301698741/job/28513821557#step:2:2004
touch as a workaround, I get the mentioned error:https://github.com/fiftydinar/gidro-os/actions/runs/10301698741/job/28513821557#step:2:2004
FI added the exact step where it fails in URL now
Ahow do you build the image wait
Ais this an ostree image or an oci iamge
FBlueBuild, ostree image
Aostree you must use always /usr/etc
Aoci you must use always /etc
Fhmm, interesting
Kbluebuild is oci though, no?
Ai see a bunch of ostree commit in there
Kthat error is very strange
Aand a bunch of cursed mount
Fwait a sec, we use ostree container commit
Fidk if that counts as ostree container or what
For just using ostree instruction in OCI
Auh i dont think its called ostree container commit, that one does a bit of cleanup in var
Alet me pull an oci image and see whats going on in etc
FA
Aedited just fine
Aimage was
ghcr.io/ublue-os/bazzite-deck:40-20240627Aalso theres no rush to fix, if the rsync command works it works
Fthose little errors scare me if some regressions goes unnoticed
Ayeah me too bc now rechunk with rsync will mess with some /etc permissions
Abut /etc being read only kind of points me to using ostree
K--force-allowreplace is also a no, doesn't change this behavior
Kso we're down to replace file in containerfile, or move it back to /usr/etc in the meantime
KI will likely do the latter
RWhat's the primary issue with /usr/etc/? Is it just that it's not officially supported by Fedora?
Or is there some other factor forcing us to change?
Or is there some other factor forcing us to change?
Aits that its implicitly merged with /etc during deployment by rpm-ostree
Aand now that we are using rechunk, either we have to explicitly merge it and choose how or the image will not boot
Aessentially rpm-ostree has a little path rewriter that converts /etc to /usr/etc and leaves /usr/etc alone
Aif the rsync command in rechunk does not cause issues it essentially is not a major problem
Abut the problem is the rsync command will rewrite the dir permissions now
RIf needed, overwriting the existing file during the COPY isn't as bad as I thought. It's just two places where this is needed
Ai guess you relied on this behavior rn because with e.g. yafti you placed your modified file with ublue on /usr/etc
Aand then rpm-ostree skipped the error when installing and automerged during deployment
KGitHub
Without this, this package conflicts with containers-common
We should likely repackage that with our changes and have this package provide it to fix this properly.
We should likely repackage that with our changes and have this package provide it to fix this properly.
Kthere we go
F@antheas BlueBuild image is OCI, yes, got confused for a moment on ostree vs OCI
AAtried to cleanup the wording
J@Kyle Gospo do I need to remove the PR you sent to bluefin? I'm not using the rechunker atm
KNo, if that's building and tests well go for it
Kthis is about main
Jack
