Both top-level 'rosetta' and 'vmOpts.vz.rosetta' are configured. Using vmOpts.vz.rosetta. Top-level 'rosetta' is deprecated.

[komapa]

Description

We start colima with these flags:

"colima", "start",
		"--cpu", cpuCores,
		"--memory", memory,
		"--disk", disk,
		"--vm-type", "vz",
		"--mount-type", "virtiofs",
		"--vz-rosetta",

Version

0.9.1

Operating System

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

Output of colima status

❯ colima status -e
INFO[0000] colima is running using macOS Virtualization.Framework
INFO[0000] arch: aarch64
INFO[0000] runtime: docker
INFO[0000] mountType: virtiofs
INFO[0000] docker socket: unix:///Users/XXX/Library/Preferences/colima/default/docker.sock
INFO[0000] containerd socket: unix:///Users/XXX/Library/Preferences/colima/default/containerd.sock
INFO[0000] cpu: 10
INFO[0000] mem: 18GiB
INFO[0000] disk: 100GiB

Reproduction Steps

colima start and then you can see that warning written as the VM starts.

Both top-level 'rosetta' and 'vmOpts.vz.rosetta' are configured. Using vmOpts.vz.rosetta. Top-level 'rosetta' is deprecated.

Expected behaviour

No warning is emitted

Additional context

This is the lima code block: https://github.com/lima-vm/lima/blob/b114156708f29e989e5fbffbfa1e9ba64598f2a7/pkg/driver/vz/vz_driver_darwin.go#L168

//nolint:staticcheck // Migration of top-level Rosetta if specified
	if (vzOpts.Rosetta.Enabled == nil && vzOpts.Rosetta.BinFmt == nil) && (!isEmpty(cfg.Rosetta)) {
		logrus.Debug("Migrating top-level Rosetta configuration to vmOpts.vz.rosetta")
		vzOpts.Rosetta = cfg.Rosetta
	}
	//nolint:staticcheck // Warning about both top-level and vmOpts.vz.Rosetta being set
	if (vzOpts.Rosetta.Enabled != nil && vzOpts.Rosetta.BinFmt != nil) && (!isEmpty(cfg.Rosetta)) {
		logrus.Warn("Both top-level 'rosetta' and 'vmOpts.vz.rosetta' are configured. Using vmOpts.vz.rosetta. Top-level 'rosetta' is deprecated.")
	}

[abiosoft]

This is currently being fixed and would soon be merged.

[shubhsavani-sys]

any update on this fix? I am also running into the same issue. Is there an alternative way to pass the rosetta flag? Currently on version 0.9.1

[daisenberg]

Hey, any update on when the fix will go in? Thanks.

[madhavajay]

@abiosoft If I understand correctly, this is a pretty big blocker for Github Actions? Are you able to link to the PR in case we want to try it ourselves?

[abiosoft]

The fix has been merged.

You can verify by installing the development version with brew install --head colima.

[nathanblair]

🤔 I might be missing something here but I don't see it reflected in the current HEAD install

fsh ❯ colima version
colima version HEAD-ccd5ddd
git commit: ccd5ddd03ee07373160464840e747e5e0e587da1

fsh ❯ colima start -z --vz-rosetta -a host -c 12 -m 32 --very-verbose
...
> Terminal is not available, proceeding without opening an editor
> Both top-level 'rosetta' and 'vmOpts.vz.rosetta' are configured. Using vmOpts.vz.rosetta. Top-level 'rosetta' is deprecated.
> Both top-level 'rosetta' and 'vmOpts.vz.rosetta' are configured. Using vmOpts.vz.rosetta. Top-level 'rosetta' is deprecated.
> Starting the instance "colima" with internal VM driver "vz"
...