colima template does not show defaults

[gereog]

Reproduction Steps

1. brew install colima
2. colima template
3. save the template file

Expected behaviour

No colima behaviour should change

Actual behaviour

colima won't even start anymore, because colima template changed the vmType to qemu which I didn't have installed.

After fixing that, I still have to face the problem that fsevents are not being reflected on the container, because colima template changed mountInotify to false.

Description

colima template doesn't show the defaults the first time you use it, which is much less helpful than if it simply showed the defaults.

I have so far noticed two lines in colima template that are not the same as what colima start --help and the GitHub docs say that the default values should be:

• vmType: qemu
• mountInotify: false.

According to other colima docs and colima start --help, these should be vz and true respectively.

I would expect colima template to be a command to edit colima start's default values.

I also would find it useful to be able to use colima template to find out what my current defaults are.

It is very unhelpful that running colima template once can actually change your defaults, and it would be more helpful if colima template accurately showed you what the defaults are.

Version

colima version 0.8.0
git commit: 9c08cff339f087c0600d9d56af7b5fbcfe02e287

runtime: docker
arch: aarch64
client: v27.3.1
server: v27.3.1
limactl version 1.0.1
zsh: command not found: qemu-img

Operating System

• macOS Intel <= 13 (Ventura)
• macOS Intel >= 14 (Sonoma)
• Apple Silicon <= 13 (Ventura)
• Apple Silicon >= 14 (Sonoma)
• Linux

Output of colima status

No response

Additional context

I used colima template to increase the default amount of memory allocated for the virtual machine.

But after writing the file, I was surprised to find that colima start didn't work at all anymore! That's because colima template changed vmType to qemu.

Then later, when trying to continue development, I noticed hot-reloading wasn't working!

That's because colima template changed mountInotify to false.

It took an hour to debug this, I got sucked into many older issues online about fs events and hot-reloading not working on colima, and tried many different solutions.

I didn't expect that running colima template once would have changed mountInotify to false, especially not when colima start --help says --mount-inotify is true by default.

There may still be other surprises that running colima template once has introduced.

[fusionfox]

As of #848:

Inotify flag --mount-inotify now defaults to true

Although it is not mentioned in the release notes for v0.6.0

@abiosoft does the mountInotify value in colima/embedded/defaults/colima.yaml need to be updated to reflect this?

Is the comment in that file that says it is experimental still true?