How to set bind mounts into the Dockerfile

[nicolaspernoud]

Hello,

I would like to get custom bind mounts sets into the Dockerfile, so that they can be altered by creating an upgrade image, and not with cloud init.

That seems possible by putting a yaml file in /system/oem like in https://github.com/mudler/dockerfiles/blob/master/kairos-orin-docker/Dockerfile .

Is that a good idea ? Any drawbacks ?

Putting them to /oem/ does not work, they are not present in the running VM.

Also, when creating a efi or bios image with auroraboot, the install section of cloud init is not played, and the bind_mounts from the install are not activated. Any way to circumvent this ?

Best regards, and thanks for all the work on kairos !

[jimmykarily]

Putting it in /system/oem sounds ok to me. I don't see why not (especially since it works :D)

[nicolaspernoud]

Ok, and thanks for the answer.
Additional question : it seems that the "install:" part of a cloud-init is played when installing from an iso created with auroraboot, but that it is not "cold played" when creating a raw image (efi) ? Is that normal ? Did that change at some point during kairos development (i think it used to work) ?

[Itxaka]

Hey @nicolaspernoud

yes indeed, when creating raw images, the install part and its phases/hooks (install.pre, install.post, etc...) are not run at all. This was always the case, after all when creating a raw image you are creating the final image (disk installed one) so the install is never really run. This is due how images are supposed to be used (cloud services or brun into a usb/sd card to boot from them) and they never had that phase as they never really install during runtime, only during build time.

[nicolaspernoud]

Thanks for your reply, that's very good to know...
Maybe it would be nice to have it clearly written in the docs, with an how to do bind_mounts for raw images...