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

No usable default provider could be found #82

Open
rbohling opened this issue Oct 7, 2023 · 1 comment
Open

No usable default provider could be found #82

rbohling opened this issue Oct 7, 2023 · 1 comment

Comments

@rbohling
Copy link

rbohling commented Oct 7, 2023

Describe the bug
A clear and concise description of what the bug is.
sudo vagrant up i get an error
To Reproduce
Steps to reproduce the behavior:
cd ~/bin/rhcsa8env
vagrant up
No usable default provider could be found for your system.

Vagrant relies on interactions with 3rd party systems, known as
"providers", to provide Vagrant with resources to run development
environments. Examples are VirtualBox, VMware, Hyper-V.

The easiest solution to this message is to install VirtualBox, which
is available for free on all major platforms.

If you believe you already have a provider available, make sure it
is properly installed and configured. You can see more details about
why a particular provider isn't working by forcing usage with
vagrant up --provider=PROVIDER, which should give you a more specific
error message for that particular provider.

Expected behavior
A clear and concise description of what you expected to happen.
I expected the environment to be built.
Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: RHEL 9.2
  • Browser Firefox
  • Version

Additional context
Add any other context about the problem here.
Is it because Im running 9.2? I have Vb 7.0 installed

@rbohling rbohling changed the title No usable default proivder could be found No usable default provider could be found Oct 7, 2023
@alexbarasa
Copy link

I faced the same error but I solved by upgrading the vagrant to version 2.4 which supports the vm I am using 6.1. Alternatively you can downgrade the vm.

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