abiosoft/colima · warning

error persisting store settings: %w

Error message

error persisting store settings: %w

What it means

Warning logged when store.Set fails to record DiskFormatted=true after startup while AdditionalDisks are configured in the Lima config. Because the disk was already formatted successfully during boot, failing to persist the flag is non-fatal; colima only logs it.

Source

Thrown at environment/vm/lima/lima.go:369

		if err := configmanager.SaveToFile(conf, config.CurrentProfile().StateFile()); err != nil {
			logrus.Warnln(fmt.Errorf("error persisting Colima state: %w", err))
		}
		return nil
	})

	// save store settings
	a.Add(func() error {
		if len(l.limaConf.AdditionalDisks) == 0 {
			return nil
		}

		// startup is successful
		// if additional disk is present, then it must've been formatted correctly.
		if err := store.Set(func(s *store.Store) {
			s.DiskFormatted = true
		}); err != nil {
			// not fatal, but should be logged
			logrus.Warnln(fmt.Errorf("error persisting store settings: %w", err))
		}

		return nil
	})

}

func (l *limaVM) assertQemu() error {
	// assert qemu requirement
	sameArchitecture := environment.HostArch() == l.limaConf.Arch
	if err := util.AssertQemuImg(); err != nil && l.limaConf.VMType == limaconfig.QEMU {
		if !sameArchitecture {
			return fmt.Errorf("qemu is required to emulate %s: %w", l.limaConf.Arch, err)
		}
		return err
	}
	return nil
}

View on GitHub (pinned to c3a5f9184d)

Solutions

1. Verify the store file is writable: ls -la ~/.colima/<profile>/ and fix ownership if needed
2. Free disk space on the home volume
3. Avoid running concurrent colima commands against the same profile
4. If the store is corrupted, 'colima delete' and re-create the profile (the disk flag is re-set on next start)

Non-fatal by design: colima swallows the store.Set error into a warning. If you call store.Set in your own tooling, wrap it: if err := store.Set(func(s *store.Store){ s.DiskFormatted = true }); err != nil { log.Warn(err) } and keep going.

When it happens

Trigger: l.limaConf.AdditionalDisks is non-empty and store.Set cannot write the profile store (permissions, disk full, corrupted store file, concurrent writers).

Common situations: Started with 'colima start --disk ...' or --additional-disks and the host filesystem is full; the store JSON under ~/.colima/<profile> is corrupted or root-owned; simultaneous colima commands on one profile.

Related errors

• error writing store file: %w
• error persisting runtime settings: %w
• error retrieving runtimes: %w
• error deleting container data: %w
• error copying VM: %w

AI-assisted analysis of abiosoft/colima@c3a5f9184d (2026-08-15). Data as JSON: /api/errors/3db02d7815613f14. Report an issue: GitHub.