How can I specify the native mount type for a mount (i.e. --mount) as part of a launch command?

[nalcabio-tom]

Or is there a way to create a vm without starting it?

[ricab]

Hi @nalcabio-tom, I am afraid that's not currently possible. You can only choose native with the mount command (over existing instances). May I ask why you need it at launch?

[nalcabio-tom]

Thanks for taking the time to respond, @ricab . Because I'd like it to be used by cloud-init. I want some other way than trying to shove everything we already have for provisioning into one yaml file. Is there another way I've missed?

[ricab]

I see. I feared that would be the case. You can use classic mounts at launch only, but I believe they are only done after cloud-init finishes.

We are working on other storage options, FWIW, but it will take a while before we can release them.

[nalcabio-tom]

We're switching to Debian Trixie. Classic mounts are problematic on trixie shall we say.

[nalcabio-tom]

Thanks again @ricab for taking the time to respond

[nalcabio-tom]

Just to be clear, our development laptops are Ubuntu LTS. We have a fleet of Raspberry PIs which are currently running Raspberry PI OS currently based on bookworm which we hope will switch to trixie soon. We were running vagrant and a bookworm "box" to develop and test everything on our laptops, but due to vagrant's recent license change, debian isn't maintaining its vagrant boxes anymore. We're looking for a replacement for vagrant that will allow us to run stock trixie images on our laptops. We don't use cloud-init to provision our Raspberry PIs so we'd like a solution that won't require us to switch to that just for local development and test.