coreos-home-server icon indicating copy to clipboard operation
coreos-home-server copied to clipboard

Switch base image?

Open parkan opened this issue 11 months ago • 2 comments

Thank you for the tight writeup and matching (and maintained!) repo for this project. I had no trouble building a deploy-virtual target in a toolbx on bluefin, the only thing that's missing from non-obvious dependencies is jq 😉

I am curious about switching over to the ublue coreos build since that (optionally) bundles nvidia and zfs, which I will need for my actual target. Do you know how to switch the base image this builds on? I was initially planning to just layer the packages but apparently this is weirdly kludgey and the "proper" solution remains to use coreos-assembler to make your own spin, though luckily in my case ublue already packages more or less exactly what I need.

parkan avatar Jan 19 '25 16:01 parkan

As far as deploying on bare metal is involved, you should just be able to boot the corresponding image and then point coreos-installer to the IP address and port given when running make deploy TYPE=metal HOST=... -- this does assume that the server you're deploying to is on the same (local) network as the computer you're using to build the Ignition file.

Testing alternative images on the virtual host requires a few changes to the Makefile as we assume that the image URL generally follows naming conventions used by upstream; it's an easy enough fix, I'll push something soon enough if nobody else gets to it before me.

Thanks for your kind words as well; I'm in the process of writing a few more docs and cleaning up some of the structure here for easier extensibility, which should hopefully make this an easier out-of-the-box experience for other people.

deuill avatar Jan 19 '25 16:01 deuill

ahhh yes I see, documented here https://coreos.github.io/coreos-installer/cmd/install/, I just give --image-url and it should pick it up

I guess there is limited utility to specifying this for the virtual build given that the qemu environment won't have a physical nvidia device or real drives etc, but it would still be good to be able to build on top of the target image to catch any regressions... I will PR this if I get around to adding this parameter to Makefile before you do

parkan avatar Jan 20 '25 15:01 parkan