-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[macOS] Install virtualbox on macOS-11 #4010
Conversation
9918415
GitHub is currently migrating its macos-latest runner to macOS 11: actions/runner-images#4060 Unfortunately, installing VirtualBox and Vagrant on this new version of macOS is not easy, and the current macos11 runner does not support running virtual machines using Vagrant. This issue is being fixed on actions/runner-images#4010 . Until this Pull Request is merged, use macos10 runner instead of macos-latest, to continue using Vagrant to run the SELinux testsuite in a virtual machine. Signed-off-by: Nicolas Iooss <nicolas.iooss@m4x.org>
GitHub is currently migrating its macos-latest runner to macOS 11: actions/runner-images#4060 Unfortunately, installing VirtualBox and Vagrant on this new version of macOS is not easy, and the current macos-11 runner does not support running virtual machines using Vagrant. This issue is being fixed on actions/runner-images#4010 . Until this Pull Request is merged, use macos-10.15 runner instead of macos-latest, to continue using Vagrant to run the SELinux testsuite in a virtual machine. Signed-off-by: Nicolas Iooss <nicolas.iooss@m4x.org>
GitHub is currently migrating its macos-latest runner to macOS 11: actions/runner-images#4060 Unfortunately, installing VirtualBox and Vagrant on this new version of macOS is not easy, and the current macos-11 runner does not support running virtual machines using Vagrant. This issue is being fixed on actions/runner-images#4010 . Until this Pull Request is merged, use macos-10.15 runner instead of macos-latest, to continue using Vagrant to run the SELinux testsuite in a virtual machine. Signed-off-by: Nicolas Iooss <nicolas.iooss@m4x.org>
GitHub is currently migrating its macos-latest runner to macOS 11: actions/runner-images#4060 Unfortunately, installing VirtualBox and Vagrant on this new version of macOS is not easy, and the current macos-11 runner does not support running virtual machines using Vagrant. This issue is being fixed on actions/runner-images#4010 . Until this Pull Request is merged, use macos-10.15 runner instead of macos-latest, to continue using Vagrant to run the SELinux testsuite in a virtual machine. Signed-off-by: Nicolas Iooss <nicolas.iooss@m4x.org> Acked-by: Ondrej Mosnacek <omosnace@redhat.com>
The `macos-latest` image was recently updated to macos 11 which does not include virtualbox anymore. This commit pins the previous version macos-10.15 until a more permament fix can be found. More information can be found in the discussion of this PR: nektos#840 (comment) and in the following issue and PR for the actions/virtual-environments: actions/runner-images#4060 actions/runner-images#4010 Co-authored-by: Markus Wolf <mail@markus-wolf.de>
Is it possible for this PR to be merged? |
@Neilpang unfortunately, no. It's not yet ready |
Are you aware that some users may use Vagrant/VirtualBox to test FreeBSD built without care of the "screen resolution change" limitation issue ? ref: #4060 (comment) |
who will need to change screen resolution in a github runner ? |
note: In preparation to actions/runner-images#4060 which will drop Vagrant/VirtualBox ref: actions/runner-images#4010
note: In preparation to actions/runner-images#4060 which will drop Vagrant/VirtualBox ref: actions/runner-images#4010
The `macos-latest` Github Actions virtual environment does not support VirtualBox anymore (see actions/runner-images#4060 and actions/runner-images#4010 for more details). Since we do need a virtual machine running Linux for the cozy-stack to have access to a unix filesystem and mimic our production VFS behavior, we have to switch back to using the `macos-10.15` virtual environment. Apparently Github is looking for a solution to this issue so once they do find one, we'll be able to switch again to the `macos-latest` environment.
The "macos-11" image which is becoming "macos-latest" does not include virtualbox/vagrant yet. cf actions/runner-images#4060 and actions/runner-images#4010
I believe it's much better to unblock some VirtualBox users (those who do not need UI tests) than to block 100% of your VirtualBox users. Are you open to reconsidering the current approach of removing VirtualBox completely? |
See: actions/runner-images#4010 Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
The macos-latest label moved to macOS 11. However, this image from GitHub doesn't have VirtualBox installed, and it's not clear that this will ever happen. 10.15 is still supported, though. These two issues are provided as reference: - actions/runner-images#4060 - actions/runner-images#4010
Use macos 10.15 since they're with vagrant and virt but don't use 11 and never due to missing vagrant on them. Ref: actions/runner-images#4060 actions/runner-images#4010 Signed-off-by: Arnaud Patard <apatard@hupstream.com>
Use macos 10.15 since they're with vagrant and virt but don't use 11 and never due to missing vagrant on them. Ref: actions/runner-images#4060 actions/runner-images#4010 Signed-off-by: Arnaud Patard <apatard@hupstream.com>
The "macos-11" image which is becoming "macos-latest" does not include virtualbox/vagrant yet. cf actions/runner-images#4060 and actions/runner-images#4010
The "macos-11" image which is becoming "macos-latest" does not include virtualbox/vagrant yet. cf actions/runner-images#4060 and actions/runner-images#4010
The `macos-10.15` runner is depecrated since 5/31/22 and will be unsupported by 12/1/22 (see actions/runner-images#5583). We did not upgrade before because the `macos-11` runner does not provide VirtualBox which we need to create an Ext filesystem for `cozy-stack` (see actions/runner-images#4010 for more details on previous attempts to add it to `macos-11`) and it was not yet available in the `macos-12` runner. It's now available in `macos-12` (see actions/runner-images#5594) so we can upgrade to `macos-12`.
The `macos-10.15` runner is depecrated since 5/31/22 and will be unsupported by 12/1/22 (see actions/runner-images#5583). We did not upgrade before because the `macos-11` runner does not provide VirtualBox which we need to create an Ext filesystem for `cozy-stack` (see actions/runner-images#4010 for more details on previous attempts to add it to `macos-11`) and it was not yet available in the `macos-12` runner. It's now available in `macos-12` (see actions/runner-images#5594) so we can upgrade to `macos-12`.
The `macos-10.15` runner is deprecated since 5/31/22 and will be unsupported by 12/1/22 (see actions/runner-images#5583). We did not upgrade before because the `macos-11` runner does not provide VirtualBox which we need to create an Ext filesystem for `cozy-stack` (see actions/runner-images#4010 for more details on previous attempts to add it to `macos-11`) and it was not yet available in the `macos-12` runner. It's now available in `macos-12` (see actions/runner-images#5594) so we can upgrade to `macos-12`.
GitHub is currently migrating its macos-latest runner to macOS 11: actions/runner-images#4060 Unfortunately, installing VirtualBox and Vagrant on this new version of macOS is not easy, and the current macos-11 runner does not support running virtual machines using Vagrant. This issue is being fixed on actions/runner-images#4010 . Until this Pull Request is merged, use macos-10.15 runner instead of macos-latest, to continue using Vagrant to run the SELinux testsuite in a virtual machine. Signed-off-by: Nicolas Iooss <nicolas.iooss@m4x.org> Acked-by: Ondrej Mosnacek <omosnace@redhat.com>
Description
Installation
VirtualBox
on macOS-11 viabrew
.Added AppleScript to approve
VirtualBox
developer in security preferences of OS.Execution of
commonutils.sh
moved to section beforeXcode
installation inmacOS-11
template, because we need reboot system afterVirtualBox
installation.Related issue:
internal #2672
Check list