-
Notifications
You must be signed in to change notification settings - Fork 378
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
Implement vagrant for kernel-specific testing #194
Comments
I will take up this issue. According to @oxr463 via our private chat, we will want to implement CentOS, Debian, and Alpine vagrant boxes to start off with. Please see: https://www.vagrantup.com/docs/virtualbox/boxes.html |
@eredisg any progress on this one? |
We do not need to create the base boxes, just use these: uname -a
Linux alpine310.localdomain 4.19.80-0-virt #1-Alpine SMP Fri Oct 18 11:51:24 UTC 2019 x86_64 GNU/Linux Linux localhost.localdomain 3.10.0-957.12.2.el7.x86_64 #1 SMP Tue May 14 21:24:32 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Linux stretch 4.9.0-9-amd64 #1 SMP Debian 4.9.168-1+deb9u2 (2019-05-13) x86_64 GNU/Linux |
Requires installing the vagrant-sshfs plugin, (See: https://github.com/dustymabe/vagrant-sshfs#getting-started). |
This comment has been minimized.
This comment has been minimized.
* Create howto-devel.rst * Update howto-release.rst Bug: #194
Originally posted by @oxr463 in #111 (comment)
See: OpenVPN/openvpn#45
The text was updated successfully, but these errors were encountered: