Closed piotrpawlaczek closed 7 months ago
Thanks for the report, @piotrpawlaczek. I was interested in trying things out in the M1 runners since I saw the post announcing them. Will give this a try this week. 👍
Reported the /usr/local/share
permission issue to Github: https://github.com/actions/runner-images/issues/9272
Will skip download the binaries to move straight to the colima VM part of the problem.
@piotrpawlaczek the issue seems to come from lack of support for nested virtualization in the M1 processor. This prevents QEMU or even Virtualization.framework from working.
QEMU will report {"level":"debug","msg":"qemu[stderr]: qemu-system-aarch64: Error: HV_UNSUPPORTED","time":"2024-02-01T19:34:57Z"}
Trying to use Virtualization.framework in Colima through --vm-type=vz
will report {"level":"fatal","msg":"Error Domain=VZErrorDomain Code=2 Description=\"Invalid virtual machine configuration. Virtualization is not available on this hardware.\" UserInfo={\n NSLocalizedFailure = \"Invalid virtual machine configuration.\";\n NSLocalizedFailureReason = \"Virtualization is not available on this hardware.\";\n}","time":"2024-02-01T19:36:49Z"}
.
There's nothing I can do besides see if Github can answer my pleas.
I experimented with this on #27, by the way. Used https://github.com/mxschmitt/action-tmate to ssh into the runner, tried to start Colima and checked logs.
@piotrpawlaczek I can't make this work because of the limitations I mentioned (lack of software support in all cases, lack of hardware support in some), I added a notice and a check that I can't support M-series processors as of today (see #28).
I'm happy to support the M2 and M3 processors when Apple adds the software support.
Hello @douglascamata, I appreciate your discovery and insights. It's unfortunate, though. I was really looking forward to macos-14, especially since our arm64 builds are quite time-consuming on non-native GitHub runners. However, it appears that installing the Docker daemon is not straightforward given the circumstances.
@piotrpawlaczek that is indeed very unfortunate. I was also excited for this, as I love the performance of my M1 Pro machine. Now we have to choose between Docker or M1… unless GitHub finds a way to give us shareable runners that aren’t VMs.
Could be possible if they had a special flavor of runners that ran our actions directly in an instance of Colima, without access to the host. They would make this whole project obsolete, for the best.
Action crashes on m1 GitHub runner.
Lima https://github.com/piotrpawlaczek/setup-docker-macos-action/actions/runs/7745160104/job/21120522041
Colima https://github.com/piotrpawlaczek/setup-docker-macos-action/actions/runs/7745338011/job/21121084290