Skip to content
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

Big Sur - Commands no longer running #188

Open
atticus7 opened this issue Dec 2, 2020 · 2 comments
Open

Big Sur - Commands no longer running #188

atticus7 opened this issue Dec 2, 2020 · 2 comments

Comments

@atticus7
Copy link

atticus7 commented Dec 2, 2020

Since upgrading my Mac to Big Sur (11.0.1), I'm no longer able to vagrant up or run any other commands via Vagrant Manager. I've tried uninstalling and starting from scratch. I can detect all the vagrants on my system, but that's about all. If I vagrant up using the CLI and then refresh, it's unable to detect that the vagrant is running. And vagrant halt won't work either.

All commands work as expected via the CLI on Terminal/iTerm however.

@atticus7
Copy link
Author

No-one else experienced this then?

@JalenWasHere
Copy link

@atticus7 By any chance was this the error you were getting?

/Users/jalen/.vagrant.d/gems/3.1.4/gems/public_suffix-5.0.5/lib/public_suffix/rule.rb:129:in `count': invalid byte sequence in US-ASCII (ArgumentError)

I've made a fork of the project that updates dependencies and fixes the Vagrant actions.

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

No branches or pull requests

2 participants