-
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
Add VirtualBox and Vagrant for macOS instances #433
Comments
Did you stop any active Virtualbox instances before upgrading? That was something I forgot to do. |
I would also be interested in this! Or at least approving the virtualbox team id kext, which allows folks to install virtualbox themselves. |
Is this already supported on Linux then? |
No, only macOS instances seem to support nested virtualization currently |
Hello, pull request with vagrant and virtualbox was merged and changes would be added to next images rollout. |
Only for macOS though? The Linux issue was closed. |
@oxr463 , Yes, only for macOS. |
Hello, Vagrant and VirtualBox were added to macOS. If you have any concerns feel free to reopen the issue. |
…er with fuse errors. This is most likely because fuse requires a kernel module to be loaded, and for that to work in a Docker container, then the docker host must have that module loaded. 2020-05-31T21:33:35.5478138Z + chmod +x /tmp/appimagetool.AppImage 2020-05-31T21:33:35.5487678Z + mkdir dist 2020-05-31T21:33:35.5517125Z + /tmp/appimagetool.AppImage /tmp/kivy_appdir dist/helloWorld.AppImage 2020-05-31T21:33:35.5522850Z fuse: device not found, try 'modprobe fuse' first 2020-05-31T21:33:35.7058092Z open dir error: No such file or directory 2020-05-31T21:33:35.7058725Z + uname -a The question is: am I running a container in a container? Because if the ubuntu docker host is actually a VM with debain running inside it as a container, then maybe I can load the fuse module on the docker host before going into the container? Let's try it. fwiw, this is not necessary on gitlab's shared runners. I also found this indicating that github had no desire to add modules totheir shared runners :\ * https://github.saobby.my.eu.orgmunity/t/custom-linux-kernel-module/17194 And I learned that apparently the GitHub MacOS shared runners support nested virtualization and have vagrant & virtualbox installed by default. Intersting.. * actions/runner-images#183 * actions/runner-images#433 (comment)
As discovered by Nicholas Iooss [1], GH Actions now supports HW-accelerated Linux VMs at least on macOS runners [2], so we can finally migrate the CI away from Travis. The new check uses Vagrant to provision the Fedora VM, as this is the simplest way to get it to work on macOS. Unfortunately there is no Rawhide image provided in the official Vagrant repos, so for now the testsuite is run only on Fedora 33. Adding support for Rawhide would be more complex, so I'm skipping it for now. (But I hope to add it eventually.) [1] https://patchwork.kernel.org/project/selinux/patch/20201230200821.3454892-1-nicolas.iooss@m4x.org/ [2] actions/runner-images#433 (comment) Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
As discovered by Nicholas Iooss [1], GH Actions now supports HW-accelerated Linux VMs at least on macOS runners [2], so we can finally migrate the CI away from Travis. The new check uses Vagrant to provision the Fedora VM, as this is the simplest way to get it to work on macOS. Unfortunately there is no Rawhide image provided in the official Vagrant repos, so for now the testsuite is run only on Fedora 33. Adding support for Rawhide would be more complex, so I'm skipping it for now. (But I hope to add it eventually.) [1] https://patchwork.kernel.org/project/selinux/patch/20201230200821.3454892-1-nicolas.iooss@m4x.org/ [2] actions/runner-images#433 (comment) Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
As discovered by Nicholas Iooss [1], GH Actions now supports HW-accelerated Linux VMs at least on macOS runners [2], so we can finally migrate the CI away from Travis. The new check uses Vagrant to provision the Fedora VM, as this is the simplest way to get it to work on macOS. Unfortunately there is no Rawhide image provided in the official Vagrant repos, so for now the testsuite is run only on Fedora 33. Adding support for Rawhide would be more complex, so I'm skipping it for now. (But I hope to add it eventually.) [1] https://patchwork.kernel.org/project/selinux/patch/20201230200821.3454892-1-nicolas.iooss@m4x.org/ [2] actions/runner-images#433 (comment) Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
As discovered by Nicholas Iooss [1], GH Actions now supports HW-accelerated Linux VMs at least on macOS runners [2], so we can finally migrate the CI away from Travis. The new check uses Vagrant to provision the Fedora VM, as this is the simplest way to get it to work on macOS. Unfortunately there is no Rawhide image provided in the official Vagrant repos, so for now the testsuite is run only on Fedora 33. Adding support for Rawhide would be more complex, so I'm skipping it for now. (But I hope to add it eventually.) [1] https://patchwork.kernel.org/project/selinux/patch/20201230200821.3454892-1-nicolas.iooss@m4x.org/ [2] actions/runner-images#433 (comment) Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
As discovered by Nicholas Iooss [1], GH Actions now supports HW-accelerated Linux VMs at least on macOS runners [2], so we can finally migrate the CI away from Travis. The new check uses Vagrant to provision the Fedora VM, as this is the simplest way to get it to work on macOS. Unfortunately there is no Rawhide image provided in the official Vagrant repos, so for now the testsuite is run only on Fedora 33. I'd like to add Rawhide in the future, but let's start with the low-hanging fruit. [1] SELinuxProject/selinux@316a4f8 [2] actions/runner-images#433 (comment) Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
This seems removed on macOS 11.0 instances? 😢 |
@AkihiroSuda, There is no stable VirtualBox release for macOS Big Sur. |
VirtualBox 6.1.16 seems working fine on macOS 11.1 on my local MacBook, though I haven't tested macOS 11.0. |
As discovered by Nicholas Iooss [1], GH Actions now supports HW-accelerated Linux VMs at least on macOS runners [2], so we can finally migrate the CI away from Travis. The new check uses Vagrant to provision the Fedora VM, as this is the simplest way to get it to work on macOS. Unfortunately there is no Rawhide image provided in the official Vagrant repos, so for now the testsuite is run only on Fedora 33. I'd like to add Rawhide in the future, but let's start with the low-hanging fruit. [1] SELinuxProject/selinux@316a4f8 [2] actions/runner-images#433 (comment) Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
As discovered by Nicholas Iooss [1], GH Actions now supports HW-accelerated Linux VMs at least on macOS runners [2], so we can finally migrate the CI away from Travis. The new check uses Vagrant to provision the Fedora VM, as this is the simplest way to get it to work on macOS. Unfortunately there is no Rawhide image provided in the official Vagrant repos, so for now the testsuite is run only on Fedora 33. I'd like to add Rawhide in the future, but let's start with the low-hanging fruit. [1] SELinuxProject/selinux@316a4f8 [2] actions/runner-images#433 (comment) Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
As discovered by Nicholas Iooss [1], GH Actions now supports HW-accelerated Linux VMs at least on macOS runners [2], so we can finally migrate the CI away from Travis. The new check uses Vagrant to provision the Fedora VM, as this is the simplest way to get it to work on macOS. Unfortunately there is no Rawhide image provided in the official Vagrant repos, so for now the testsuite is run only on Fedora 33. I'd like to add Rawhide in the future, but let's start with the low-hanging fruit. [1] SELinuxProject/selinux@316a4f8 [2] actions/runner-images#433 (comment) Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
Opened #2999 for Big Sur |
FYI, now that the Here are my workflow files: |
…virtualization MacOS supports it, see actions/runner-images#433
Tool information
brew
, or the latest version if possible.Area for Triage:
Question, Bug, or Feature?:
Feature
Virtual environments affected
(Only macOS instances seem to support nested virtualization currently)
Can this tool be installed during the build?
No, because of the VirtualBox's kernel extension issue: #429
So VirtualBox needs to be preinstalled as in HAXM.
Are you willing to submit a PR?
No
The text was updated successfully, but these errors were encountered: