https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# elemental
a
This message was deleted.
c
This is my first time with elemental so it could be user error. I do see that arm hardware is in development too. I am using raspberry pi 5s too
f
Which 
baseImage
did you use? The one in the example is no longer available for me, I would try with 
<http://registry.suse.com/suse/sl-micro/6.0/baremetal-os-container:latest|registry.suse.com/suse/sl-micro/6.0/baremetal-os-container:latest>
(the baremetal flavor channel should be installed by default when you install Elemental from Rancher) Also if you configured users in the `MachineRegistration`'s cloud-config, you should be able to login, or does the boot fail?
c
Hey thanks for the response Andrea, I did notice the base image in the document no longer existed so I tried 2 approaches. Updating the image to 
6.1
and using the 
devlegacy
image. Both led to the same issue. Here is my Seed image yaml
Copy code
# <https://elemental.docs.rancher.com/raspi-disk>
apiVersion: elemental.cattle.io/v1beta1
kind: SeedImage
metadata:
  name: pi-img
  namespace: fleet-default
spec:
  type: raw
  baseImage: registry.opensuse.org/isv/rancher/elemental/devlegacy/containers/suse/sl-micro/6.0/baremetal-os-container
  targetPlatform: linux/arm64
  registrationRef:
    apiVersion: elemental.cattle.io/v1beta1
    kind: MachineRegistration
    name: pi
    namespace: fleet-default
For my Machine registration, ive tried using the default machine registration and a scaled down version
Copy code
apiVersion: elemental.cattle.io/v1beta1
kind: MachineRegistration
metadata:
  name: pi
  namespace: fleet-default
spec:
  config:
    cloud-config:
      users:
        - name: root
          passwd: root
    elemental:
      install:
        reboot: true
        snapshotter:
          type: btrfs
      reset:
        reboot: true
        reset-oem: true
        reset-persistent: true
The boot appears to work. I get a login prompt (hostname localhost) but my user cloud-config doesnt seem to apply. I see one of the elemental services are failed with systemd. I think 
elemental-reset-agent
? or something like that. My thoughts are that because of that failure, cloud-init doesnt get ran so my user/password doesnt get set
Im not trying to do anything special here btw. Just a single rasp pi. No disks (other than SD card) or anything fancy.... yet lol
f
elemental-register-reset
service. The raw image is a recovery partition, from this partition the 
elemental-register
tries to "reset" the system, which acts as an installation/factory reset of the system. So one thing I'm thinking about is that maybe the disk is too small, normally it should be around 4 times the image size (I think baremetal flavor is around 1GB)
and indeed this failure is preventing the MachineRegistration to be applied
c
Yep that was deff it. So my pi SD card is 64GB. Im using etcher to install it
Thanks for confirming that too
f
you can workaround it by maybe remastering one image to include a "static" cloud config in 
/system/oem
, this way your user settings should always be applied , for example `/system/oem/custom-login.yaml`:
Copy code
#cloud-config
users:
- name: "root"
  passwd: "root"
you can follow the first part only, you don't need to build an ISO image to build a raw disk type
c
Okay I see, that way I can login to see what is actually failing with the elemental-register-reset. That makes sense
f
indeed, since you are remastering the image you can also edit the unit file in 
/usr/lib/systemd/elemental-register-reset.service
the build command will invoke this unit, so make sure that exists, but maybe it can just run a dummy command instead and you can run 
elemental-register --debug --reset
manually
last but not least, you can set this flag to false to prevent the system from rebooting after reset is successful, so you have time to inspect logs if you want and make sure everything is right 
MachineRegistration.spec.elemental.reset.reboot: false
c
That sounds like a good idea. Ill give this approach a try. Thanks for all the tips and help!
Thanks for the tip. I was able to access the pi to see what the elemental service is complaining about. it appears the tpm device isn't available which is the problem. I don't suppose you have any idea on how to add tpm? Maybe pi4 had tpm. Otherwise I will Google around
Actually looks like I may have to buy it. I assume that whoever wrote that "how to" page for raspberry pi had a tpm module already. Bummer they didn't call that out as a prereq. Anyway thanks a bunch for all the help!
f
You can use a software emulated alternative to tpm: https://elemental.docs.rancher.com/authentication#tpm-alternatives
or use other identification methods
c
Thanks I saw that too and that got me passed tpm but now I'm having cert/DNS issues that I'm working around. I think I need to get away from that devlegacy base image and use the latest suse image
Open in Slack
PreviousNext
Powered by