-
-
Notifications
You must be signed in to change notification settings - Fork 422
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
brew services start colima
not working as expected
#1265
Comments
The same experience, have to start it manually. On top of that have to start as root to be able to build any image. |
Same issue, also on Apple Silicon >= 14. For me, $ brew services start colima
Bootstrap failed: 5: Input/output error
Try re-running the command as root for richer errors.
Error: Failure while executing; `/bin/launchctl bootstrap gui/501 /Users/avi/Library/LaunchAgents/homebrew.mxcl.colima.plist` exited with 5. If it helps, here are the logs from
|
Works fine for Apple Silicom >= 14 for me :/ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
brew services start colima
not working as expected. When I run the command and restart the computer, the service does start, butcolima
doesn't.Version
❯ colima version && limactl --version && qemu-img --version
colima version 0.8.1
git commit: 96598cc
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/tt/.config/colima"
runtime: docker
arch: aarch64
limactl version 1.0.4
qemu-img version 9.2.0
Copyright (c) 2003-2024 Fabrice Bellard and the QEMU Project developers
Operating System
Output of
colima status
Reproduction Steps
colima start
and it works finebrew services start colima
and restart the computerExpected behaviour
brew services start colima
should start Docker service hence start its containers automaticallyAdditional context
Result of
cat /opt/homebrew/var/log/colima.log
Screenshot
The text was updated successfully, but these errors were encountered: