For smoke testing and e2e testing elemental iso as I understand you guys are using a nested virtualized enabled environment to execute qemu for installation elemental OS. Is my understanding correct? https://github.com/rancher/elemental/blob/main/tests/smoke/smoke_test.go Or is there any other way you are testing the elemental iso without nested virtualization?

Is there a place where I can get the elemental charts without using the OCI images?

When creating a custom image for elemental where should the registration yaml be placed? Tried to find it in the documentation but I seem to be unable to locate that information. I am trying to create a custom image by using Docker.

And place a registration yaml into the docker image and later on repackage it as an ISO

Hi, Is there public access to the Dockerfile used to build sle-micro-rancher or any kind of documentation to figure out which steps are taken? It is crucial for us to fully understand the system we ship. I found https://build.opensuse.org/package/view_file/isv:Rancher:Elemental:Stable:Teal53/node-image/Dockerfile?expand=1 but most of the crucial parts seems to happen before in sle-micro-rancher (e.g. elemtental init, installation of elemental-register, rancher-system-agent, aso.)

While I was creating a cluster I get the following error on the node

level=info msg="[Applyinator] Removing historical applied plan (retention policy count: 64) /var/lib/rancher/agent/applied/20> level=error msg="error encountered during parsing of last run time: parsing time \"\" as \"Mon Jan _2 150405 MST 2006\": ca> level=error msg="error loading x509 client cert/key for probe kube-apiserver (/var/lib/rancher/k3s/server/tls/client-kube-api> level=error msg="error loading CA cert for probe (kube-apiserver) /var/lib/rancher/k3s/server/tls/server-ca.crt: open /var/li> level=error msg="error while appending ca cert to pool for probe kube-apiserver" level=error msg="error loading CA cert for probe (kube-controller-manager) /var/lib/rancher/k3s/server/tls/kube-controller-ma> level=error msg="error while appending ca cert to pool for probe kube-controller-manager" level=error msg="error loading CA cert for probe (kube-scheduler) /var/lib/rancher/k3s/server/tls/kube-scheduler/kube-schedul> level=error msg="error while appending ca cert to pool for probe kube-scheduler" level=info msg="[Applyinator] Removing historical applied plan (retention policy count: 64) /var/lib/rancher/agent/applied/20>

Note: the vm is behind a proxy. I have added the proxy settings in the machine registration

Any idea

📣 Elemental Global Online Meetup 📣 I'm extremely stoked to announce that I'll be co-hosting the Global Online Meetup for Elemental today at 11 AM EST along with @hundreds-hospital-60917 and @sticky-tailor-45974. We'll be delving into Elemental and some of its cool new features and we hope you'll join us there. P.S. Please bring all the questions you have and we'll try getting to as many as possible during the course of the session💚 Link to join us live on Youtube: https://www.youtube.com/live/-uenjgsxI5U

Hello, has anybody created extra partition for elemental. I am trying to modify cloud-init file for it.

📣 Elemental Masterclass 📣 After the resounding success of the Global Online Meetup for the Elemental project, held last week, I will be going live with @many-tiger-3407, @sticky-tailor-45974, and @hundreds-hospital-60917 today to dive deep into some features from its latest release with a Masterclass at 11 AM EST on LinkedIn and Youtube. P.S. Please bring your questions & we'll try getting to as many of them as possible during the course of the session 💚 Links to join us live: Youtube: https://www.youtube.com/live/rQv-chwnxdE LinkedIn: https://lnkd.in/dUF4iWuR

Howdy all, dumb question time that I can’t seem to find the answer to: Are there plans for a pre-built elemental ISO compatible/for use with the vSphere cloud provider for Rancher? (similar to RancherOS or BurmillaOS)

Hello, any Idea why an newly activated elemental in Rancher brings this error: (Rancher 2.7.5, Elemental 1.2)

Failed to pull image "<http://registry.opensuse.org/isv/rancher/elemental/staging/containers/rancher/elemental-operator/5.3:1.2.5|registry.opensuse.org/isv/rancher/elemental/staging/containers/rancher/elemental-operator/5.3:1.2.5>": rpc error: code = NotFound desc = failed to pull and unpack image "<http://registry.opensuse.org/isv/rancher/elemental/staging/containers/rancher/elemental-operator/5.3:1.2.5|registry.opensuse.org/isv/rancher/elemental/staging/containers/rancher/elemental-operator/5.3:1.2.5>": failed to resolve reference "<http://registry.opensuse.org/isv/rancher/elemental/staging/containers/rancher/elemental-operator/5.3:1.2.5|registry.opensuse.org/isv/rancher/elemental/staging/containers/rancher/elemental-operator/5.3:1.2.5>": <http://registry.opensuse.org/isv/rancher/elemental/staging/containers/rancher/elemental-operator/5.3:1.2.5|registry.opensuse.org/isv/rancher/elemental/staging/containers/rancher/elemental-operator/5.3:1.2.5>: not found

Hello everyone, you may want to know that remote reset functionality has been merged to Elemental just last week. This is not released yet, but it's available upstream if you would like to experiment on it. You can find more information on the documentation: https://elemental.docs.rancher.com/next/reset We also added a troubleshooting page, if you are curious about what happens under the hood and how to debug it, in case you encounter issues: https://elemental.docs.rancher.com/next/troubleshooting-reset Let me know if the documentation can be improved or if you have any questions. Thank you.

Hello guys, I have created ISO by elemental-toolkit method. Now I am trying to deploy K3S + Fleet + System Upgrade Controller over a Elemental. I am trying to pass --cloud-init flag in elemental install. It is not working for me, neither I am getting any errors.

Hello guys, I have created ISO by elemental-toolkit method - https://rancher.github.io/elemental-toolkit/docs/development/ I have deployed deployed K3S + Fleet + System Upgrade Controller over a Elemental using cloud-init yaml configuration file - https://rancher.github.io/elemental-toolkit/docs/tutorials/k3s_and_fleet_on_vanilla_image_example/ I am able to confirm that k3s is running. The issue is that Node is not registered with the cluster and Missing kubelet configuration. as a result all Key Kubernetes components pods are in pending state.

Hello Guys, I am trying the to create docker image as suggested in the Elemental documentation using the image registry.suse.com/rancher/elemental-teal/5.3:latest RUN rpm --import <repo-signing-key-url> && \ zypper addrepo --refresh <repo_url> extra_repo && \ zypper install -y <extra_package> However i am unable to install any package in it using zypper. I tried using the Suse repositories it did not work, and it requires sle micro 5.3 repo? Is there public repo available to use for sle micro? How to install packages using zypper in sle micro 5.3? thanks, Harsha

wondering if anyone can point me in the right direction for modifying the RKE2 registries file (to add a private registry) when using Elemental. I’ve tried modifying it via a file in the

/oem

directory - but the file never seems to get written as expected

Are there any recommendation that could be followed on how to use nvidia drivers in a elemental derivative? Best approach to take?

Hi, we are introducing experimental Office hours - They are going to be bi-weekly starting next Monday 17th of September at 17:00 CET. Join the huddle in this channel. It's an opportunity to ask questions, collaborate and contribute.

Hi! I'm experiencing some "false alert" with the permission checks of the overview dashboard, We installed both the extension and the operator and also adjusted the permissions. The dashboad still shows the yellow notice about missing permissions or operator. However, using the menu I can navigate to other pages and create endpoints, mange machine inventories, etc.. So technically, everything seems to work - just the dashboad has a false assessment about missing permissions and shows the notice instead of rendering the overview page. We're using a Google auth provider - the issue might be related to that. For a local user who has assigned the "Elemental Administrator" role, the overview page is shown properly. However, explictely assigning that role also to users or roles assigned by the auth provider didn't help - those users still get the yellow notice, while actually having full access. Any hints or ideas? Thanks in advance!

Hi Team, I am trying to run GUI service via docker inside elemental OS. I had • installed dependencies • enable X11Forwarding • Export Display env variable in elemental OS. But still not allowing X server connection, getting the error shown in Screenshot -

HI, is there a way to reset a node to a fresh elemenatal state? I'm strugling with installing a k3s Cluster with the meassge "Cluster Agent can't connect" after deleting teh cluster the node is also deleted from inventory, seems i need to reinstall the whole OS or is there a way to reset the inventory to a clean state with just the OS installed and still registred or re register in the inventory with full noe install from ISO

message has been deleted

Hi 👋 I am trying to use

elemental-toolkit

but I can’t find any prebuilt image - is there anything like this available?

Is there any way to remove the read-only effect of elemental-teal? I am trying to check on how to install some drivers but I want to experiment on what commands i need to use. Constantly modifying the machine registration and rebooting is a bit of a pain.

On the Nvidia page its explained on how to install a driver using ‘transactional-update’ but this seems to be missing from Teal. Is there an alternative way on how to install the drivers? https://en.opensuse.org/SDB:NVIDIA_drivers

hi, to setup a static ip address on elemental, is this the recommended way to do? https://github.com/rancher/elemental-toolkit/blob/main/docs/content/en/docs/Examples/cloud_config.md#static-ip

when customizing Elemental via yaml files in

/oem

is there a recommended way for debugging them when they aren’t working as expected?