This message was deleted.
# elemental
a
This message was deleted.
w
Hehe the settings are for fiddling! 😉
🙂 1
But the grub-entries should be set in the config-file.. although if you use another derivative as base I'm not sure if the /etc/os-release can take precedence somehow.
a
I understand how the green image is being build using the Dockerfile etc. see it is relatively easy to create my own but for the Teal image i see no reference to a Dockerfile but only an extend from cos-system.. (at least in the previous release)
For my use case a version that builds on top of SL Micro but be great, so that is why I am looking on how to create my own version of the teal image.
w
Okay, we removed the teal example from the toolkit-repo since it was a bit confusing having both github.com/rancher/elemental (teal) and the example teal release.
a
Totally understand that one!! But maybe i am confused now and i should look at that one for my use case.
I had the impression that the elemental version was using the toolkit version
So that is why i started with the teal example in the elemental-toolkit repo
So i get the confusion 🙂
w
Hehe, I did the same thing when I started! 🙈
🙂 1
a
So to get things a bit clear.. if I want to use Teal i should better look at the elemental repo and see how i can customize that one?
The direction of the toolkit is to focus on the ‘green’ version?
w
The direction of the toolkit as I know is to not publish any supported artifacts, but rather publish all tools needed to build derivatives. The green example is used in CI to see that new PRs don't break anything.
Yes, github.com/rancher/elemental (teal) can be used as a start for customization, but be warned that it also contains an installer to run k3s/rke and connect to a rancher management cluster.
Also, elemental teal is built in OBS (build.opensuse.org) and the Dockerfiles in the base of the repo are mostly used for testing.