`XDG_CONFIG_HOME` still ignored

[tj-smith47]

Description

If you start colima for the first time with XDG_CONFIG_HOME set, it respects it and generates the config dir in the appropriate place. The next time you restart it, it creates another config directory in your home directory. I saw another issue stating this was resolved, but it's not.

Version

colima version 0.9.1
git commit: 0cbf719f5409ce04b9f0607b681c005d2ff7d94a
WARN[0000] found ~/.colima, ignoring $XDG_CONFIG_HOME...
WARN[0000] delete ~/.colima to use $XDG_CONFIG_HOME as config directory
WARN[0000] or run `mv ~/.colima "/Users/tjsmith/.config/colima"
runtime: docker
arch: aarch64
client: v28.5.1
server: v28.4.0

I don't have qemu-img, I use virtiofs, and it wasn't installed as a required package via homebrew.

Operating System

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

Output of colima status

WARN[0000] found ~/.colima, ignoring $XDG_CONFIG_HOME...
WARN[0000] delete ~/.colima to use $XDG_CONFIG_HOME as config directory
WARN[0000] or run 'mv ~/.colima "/Users/tjsmith/.config/colima"'
WARN[0000] found ~/.colima, ignoring $XDG_CONFIG_HOME...
WARN[0000] delete ~/.colima to use $XDG_CONFIG_HOME as config directory
WARN[0000] or run 'mv ~/.colima "/Users/tjsmith/.config/colima"'
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/tjsmith/.colima/default/docker.sock
INFO[0000] containerd socket: unix:///Users/tjsmith/.colima/default/containerd.sock

Reproduction Steps

1. Run colima start --cpu 11 --memory 12 --disk 120 --vm-type vz --mount-type virtiofs --mount-inotify --vz-rosetta (only ~/.config/colima exists)
2. Restart colima as a homebrew service (colima stop && brew services start colima).
3. Now ~/.colima exists

Expected behaviour

Only 1 config dir, at ~/.config/colima

Additional context

No response

[tj-smith47]

Update - I've found that this issue is specific to starting colima as a homebrew service. If you add some XML to /opt/homebrew/opt/colima/homebrew.mxcl.colima.plist before starting it the second time, it will respect the additional config:

	<key>EnvironmentVariables</key>
	<dict>
		<key>PATH</key>
		<string>/opt/homebrew/bin:/opt/homebrew/sbin:/usr/bin:/bin:/usr/sbin:/sbin</string>
		<key>XDG_CONFIG_HOME</key>
		<string>/Users/tjsmith/.config</string>
	</dict>

I'm not sure what if anything you all can do to better detect an existing colima directory and not re-create it (or even just check the most common locations) as it seems to be somewhat of a homebrew problem - but if you found a way, it would be much appreciated.

[tj-smith47]

At minimum, can we add this note to the section on auto-starting colima?
https://github.com/abiosoft/colima/blob/main/docs/FAQ.md#does-colima-support-autostart