This message was deleted.
# elemental
a
This message was deleted.
w
Hi @curved-nightfall-86418! Awesome to see you want to try elemental! for 1) it's going to be hard to debug without logs, if you could post the logs from the boot with the error message it's going to help alot! For number 2, it depends a bit on which stage you are trying to run zypper. When running the system is immutable so you won't be able to make changes, but there is some documentation how to make changes to the system here: https://rancher.github.io/elemental-toolkit/docs/customizing/runtime_persistent_changes/
c
thanks for your reply @witty-table-40840 this is the error when i try to boot with the elemental-toolkit os image
w
Hmm, could you try using the latest version of the toolkit v1.1.0? Also, you might need to install a kernel firmware package (could try
kernel-firmware-all
) in the dockerfile.
c
alright that solved the error. couple more questions: Is there a way to not make the system immutable? where should we ideally store the data if we dont want to lose the data when system crashes?
w
Glad to hear it!
The immutability question is interesting.. depends a bit on your use-case, if you only want to debug something then you can boot with the kernel parameter
rd.cos.debugrw
. If you know which directories you want to persist then you can overwrite the
/run/cos/cos-layout.env
file to add those directories as done here: https://github.com/rancher/elemental/blob/e611c52f706f00c727b6f62c747586ffc6607769/framework/files/system/oem/01_elemental-rootfs.yaml#L44C9-L44C9
The paths in
RW_PATHS
will be ephemeral but writable, the paths in
PERSISTENT_STATE_PATHS
will be writeable and persisted over reboots.