https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# elemental
a
This message was deleted.
a
If I understand correctly, following this process https://elemental.docs.rancher.com/quickstart-ui achieves the same thing except with the addition of adding machine registration and the cloud-init config? I did this, after adding 
<http://registry.suse.com/rancher/elemental-teal-channel|registry.suse.com/rancher/elemental-teal-channel>
as my OS Version Channel, and the ISO I managed to build this way results in the same issue when booting. I must be doing something dumb here!?
m
Hey Robert 👋 I think you made it right, anyway the image is missing the EFI boot file in that way. You can fix it by passing the 
--bootloader-in-rootfs
option to the build-iso command:
Copy code
docker run --rm -ti -v $(pwd):/build <http://ghcr.io/rancher/elemental-toolkit/elemental-cli:latest|ghcr.io/rancher/elemental-toolkit/elemental-cli:latest> --debug build-iso --bootloader-in-rootfs -o /build <http://registry.suse.com/rancher/elemental-teal/5.4:1.2.3|registry.suse.com/rancher/elemental-teal/5.4:1.2.3>
(@sticky-tailor-45974, @witty-table-40840, is there a better way? Should we update the docs adding --bootloader-in-rootfs?)
s
Yes we should update the docs or even consider this flag as a default
👍 1
m
Anyway, Robert, if you just want to give a try to Elemental, you can just get the containerized iso and... well, extract the iso. Something like:
Copy code
docker run -ti --rm -v .:/out <http://registry.suse.com/rancher/elemental-teal-iso/5.4:1.2.3|registry.suse.com/rancher/elemental-teal-iso/5.4:1.2.3> cp -r elemental-iso /out/
The containerized iso images are what is used to build the self-installing ISOs, i.e., the ISO building process you found in https://elemental.docs.rancher.com/quickstart-ui . What the Elemental Operator does there is to pick pre-built Elemental ISO and merge the specific registration data (so the computational overhead is minimal).
a
That’s super helpful, many thanks both.
I’ve realised another good reason why these won’t boot - 
<http://registry.suse.com/rancher/elemental-teal-iso/5.4:1.2.3|registry.suse.com/rancher/elemental-teal-iso/5.4:1.2.3>
gives me an aarch64 ISO (or at least the name of the file outputted suggests this is the case). I haven’t found a way to browse the rancher leg of the registry so forgive me if this is a daft question, but what do I need to give in order to fetch an x86 image?
Also another point of confusion - I have added the following repos/channels to Harvester in an attempt to understand the difference between them. Am I right to assume that 
elemental-teal
provides just the container images, 
elemental-teal-iso
provides these with the ISOs included, and since neither of these seem to be valid channels as far as Harvester is concerned, 
elemental-teal-channel
includes both of them side by side, presumably with some extra packaging/metadata so that Harvester can consume this as a channel?
Further to this, it seems the description in the YAML for the ISO that Harvester gets from this channel suggests it is an x86 image, despite the URI being the same as what I’m using outside of Harvester which gives me an arm image as mentioned above 🤔
OH! I bet this Docker image is doing 
uname -m
on my local machine (an M1 mac) and conditionally serving me the right ISO for my arch isn’t it…
👍 1
Yup, that was exactly it
I now have my Harvester (x86 host) VM booting into the elemental teal ISO. Looks like I have some other stuff to work out as far as the install goes but I’ll pick that up another day. If I end up settling on the Elemental stack I’d be keen to contribute to the doco as it’s taken me quite a while to decipher to this point. Very glad for this Slack channel, thanks again.
🎉 2
w
Glad to see you solved it! The toolkit docs are in a weird place right now since we want to migrate them to be next to the elemental rancher docs in https://elemental.docs.rancher.com but haven't gotten all the way yet!
👍 1
a
Hey again, another quick question - Is there any way I can pass the 
--bootloader-in-rootfs
flag (or otherwise achieve the same effect) when building seed images through the Rancher GUI?
25 Views
Open in Slack
PreviousNext
Powered by