This message was deleted.

The seedimage will lead to the creation of a pod within the same namespace (fleet-default) and same name as seedimage. I'd start looking into what happens with this pod. Also note that we do have some documentation here: https://elemental.docs.rancher.com/custom-images#create-a-custom-bootable-installation-iso And for a real example, we do build a custom image for development, it can be used as a reference: https://github.com/rancher/elemental/blob/main/Dockerfile.dev.iso We use kind load for this one to add it to the local registry of the Rancher cluster, but pushing to any other registry would be equivalent.

Yes, that right.

cp: can't stat '/elemental-iso/*.iso': No such file or directory

and, just by following the example, it will fail. So the custom image should use elemental-iso as iso path, I guess.

yes I noticed that as well, the documentation uses

/custom-iso

but should be indeed

/elemental-iso