brew services start colima. You can skip the following work-around.
- Create an executable script to run in foreground and manage colima:
cat <<-EOF | sudo tee /usr/local/bin/colima-start-fg
#!/bin/bash
export PATH="/usr/local/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin"
function shutdown() {
colima stop
exit 0
}
trap shutdown SIGTERM
trap shutdown SIGINT
# wait until colima is running
while true; do
colima status &>/dev/null
if [[ \$? -eq 0 ]]; then
break;
fi
colima start
sleep 5
done
tail -f /dev/null &
wait \$!
EOF
sudo chmod +x /usr/local/bin/colima-start-fg- Create a launchd agent to run colima automatically:
cat > $HOME/Library/LaunchAgents/com.github.abiosoft.colima.plist <<-EOF
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>com.github.abiosoft.colima</string>
<key>Program</key>
<string>/usr/local/bin/colima-start-fg</string>
<key>RunAtLoad</key>
<true/>
<key>KeepAlive</key>
<false/>
</dict>
</plist>
EOF
launchctl load -w $HOME/Library/LaunchAgents/com.github.abiosoft.colima.plist
@fardjad Is it still as simple as
brew services start colimafor you? We've been using colima at my company and it has been a huge pain. For most people, running this command and inspectingbrew servicesshows that it's stopped, and this is supported by an emptydocker psandcolima is not runningfromcolima status. We have yet to find a reliable way to manage colima, there's always something that breaks weekly for one user or another.