Homebrew never actually gets installed

[matildepark]

This is really cool! I've been giving this a shot deriving an image from the default (ghcr.io/ublue-os/silverblue-main:latest), switching into it with bootc from regular old Fedora Silverblue, and while we copy over our brew bundles into the right places, brew never actually gets installed anywhere. Unless I'm doing it wrong?

[Xarianne]

Having the same issue.

[snotrauk]

You have to copy the files to /. If you look at the source repo in which the home brew container is built. The examples it shows it just mounts it straight at /. So you can do that or copy the files from /CTX in your build scripts

[matildepark]

Indeed in your image, @snotrauk that's what's done but the flow in the default Containerfile implies brew gets copied from this dir

finpilot/Containerfile

Line 45 in ab36c37

COPY --from=ghcr.io/ublue-os/brew:latest /system_files /oci/brew

to its proper place in 10-build.sh

finpilot/Containerfile

Lines 69 to 83 in ab36c37

	## Make modifications desired in your image and install packages by modifying the build scripts.
	## The following RUN directive mounts the ctx stage which includes:
	## - Local build scripts from /build
	## - Local custom files from /custom
	## - Files from @projectbluefin/common at /oci/common
	## - Files from @projectbluefin/branding at /oci/branding
	## - Files from @ublue-os/artwork at /oci/artwork
	## - Files from @ublue-os/brew at /oci/brew
	## Scripts are run in numerical order (10-build.sh, 20-example.sh, etc.)
	RUN --mount=type=bind,from=ctx,source=/,target=/ctx \
	--mount=type=cache,dst=/var/cache \
	--mount=type=cache,dst=/var/log \
	--mount=type=tmpfs,dst=/tmp \
	/ctx/build/10-build.sh

...but then that doesn't actually happen in 10-build.sh, we just copy our Brewfiles. I don't really know the architecture well -- is it just copying /oci/brew into / in 10-build.sh?