-
-
Notifications
You must be signed in to change notification settings - Fork 420
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
Running colima on GitLab macOS runners #791
Comments
It's broken right now, has been on and off for a couple of weeks. You'll see many issues in this queue about qemu failing at start on amd64. that's what is going on here. You can find your way to most of the drama via #786 (comment) The Github Runners issue is actions/runner-images#8104 (comment) |
But vz VM type also does not work? |
Well, you're using qemu here, that's what's broken. |
It's possible that you have a completely different problem; I don't know much/anything about Gitlab, but IIRC it doesn't have an actually easily usable docker provider. |
Description
I am attempting to run colima on GitLab macOS CI runners and I simply does not start. But the issue is that I cannot find any information about why it does not start. So I am opening this issue for two reasons:
My goal is to be able to run arm64 Docker images inside macOS.
My GitLab CI configuration is as follows:
My current hypothesis is that GitLab runs macOS runners inside VM and that prevents another VM to run inside it (that nested VMs are not supported on M1). But it would be great if this would be somehow reported by colima so that next me does not spend a day debugging this.
I think this hypothesis is confirmed when I try QEMU:
See debug-only message
qemu[stderr]: qemu-system-aarch64: Error: HV_UNSUPPORTED
. My understanding is that this is because of nested virtualization?But this could be an error message when regularly running colima without
--very-verbose
flag and withvz
VM type as well.The text was updated successfully, but these errors were encountered: