-
Notifications
You must be signed in to change notification settings - Fork 10
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
Docker setup hangs forever on new macos-13
image
#37
Comments
@GlassOfWhiskey can you share the link to an action run so that I can check some logs? |
Hi @douglascamata, |
Sorry I see that logs are lost even if I forcibly stop the workflow. I paste theme hereunder for you to take a look. Here is the first
and here is the
|
same for macos-12
I have tried setting up versions of colima and lima to the same as from my previous runs which worked, but this has not helped. Looking forward to a fix as this is currently a release blocker for me. |
I’m away from the computer until the beginning of the week, but I’ll have a deep look as soon as I can. It will be fun to figure it out this time. 😅 We might have to let homebrew update and reinstall some dependencies. If you want you can try this solution by yourself in the meantime by removing the env vars I use to prevent homebrew from doing this. |
@douglascamata Thanks man! 👍
And this also have not worked but at least seems it is not freeze anymore. Output:
|
I have tried also the same but without specifying lima and colima version which resulted in:
|
@GlassOfWhiskey could you let me know please what were the versions of Lima, Colima and QEMU of your latest working build? I got hold of a computer and could make things almost work when downgrading QEMU to 9.0.2, but I've encountered a kernel panic inside the QEMU VM:
|
Hi @douglascamata, |
Hi, Are there any updates? |
Hi @douglascamata , |
Can you explain what is this PR about? |
Hi @AlvoBen, |
Unfortunately I couldn’t find a solution yet. Still trying. It’s hard to figure out whether the problem is on QEMU, the kernel used by the Colima image, in something else that came in this macOS runner update, or a combination of all the previous options. |
@douglascamata I also encountered this problem, it seems that the service did not start. The strange thing is that it was working normally a week ago.
|
@CodePrometheus it started to freeze like this after Github updated the |
I had some progress in this issue. In #40 I could fix it in |
It seems like the most recent version of QEMU is causing the SSH server inside the Colima VM to not start, which hangs all builds (see #37). I'm not exactly sure why and debugging the situation inside the action runners is kinda difficult. With this PR I am pinning QEMU to 9.0.2, which seems to work on the runner image `macos-13`. Unfortunately I couldn't make it work on the runner image `macos-12`. As this is a very old macOS version, I'm dropping support for it. If one day things get fixed, I might readd it as supported.
@GlassOfWhiskey @CodePrometheus @Noam-Br @AlvoBen: the fix I mentioned in merge. Do you mind testing by pointing your action version directly to the latest commit in the |
Thank you @douglascamata! It's working! |
Thanks for testing! I've updated the Closing this now. 🙇 |
The
macos-13
runner image has recently been updated (see here and here). In particular, Homebrew has been updated to version4.3.19
, which implies thatqemu
installation has been updated form version9.0.2
to version9.1.0
.Since then, the
colima start
command hangs forever, waiting thessh
requirement. This causes all MacOS CI steps to be skipped or interrupted by the GitHub Actions runner.The text was updated successfully, but these errors were encountered: