Skip to content

Conversation

@amanda11
Copy link
Contributor

Changes for rockylinux8 - part of StackStorm/community#88

Copy link
Member

@arm4b arm4b left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for updating it!

Just left one more minor comment.

Comment on lines +22 to +23
* Note. Problems have been found using VirtualBox 5.1 with RockyLinux 8, which were resolved
using version 6.1.
Copy link
Member

@arm4b arm4b Jan 24, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* Note. Problems have been found using VirtualBox 5.1 with RockyLinux 8, which were resolved
using version 6.1.

IMO this information is worth removing from the README now, considering Vagrantfile was fixed.

Copy link
Contributor Author

@amanda11 amanda11 Jan 24, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@armab It's not about the fix to Vagrantfile. We say you can use VirtualBox 5.0 upwards, but in my experience that is fine unless you want to use rockylinux. Rockylinux on VirtualBox 5.1 doesn't seem to work, but works if you upgrade to VirtualBox 6.1. (Whether 6.0 works I have no idea - wasn't going to try every version).
So I thought it would be useful to have it in README in case, someone else wonders why their vagrant was working perfectly fine unless they tried a rockylinux box.
The fix in Vagrantfile was needed for difference between <=6.1.26 and 6.1.28 onwards- whereby the old default host ip doesn't work on 6.1.28 onwards.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I understand now.
Makes sense, thanks for more context 👍

@amanda11 amanda11 merged commit 7ae13af into master Jan 24, 2022
@amanda11 amanda11 deleted the rocky branch January 24, 2022 21:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants