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

freebsd flaky set up vagrant #5348

Closed
crazy-max opened this issue Sep 23, 2024 · 1 comment · Fixed by #5353
Closed

freebsd flaky set up vagrant #5348

crazy-max opened this issue Sep 23, 2024 · 1 comment · Fixed by #5353

Comments

@crazy-max
Copy link
Member

crazy-max commented Sep 23, 2024

relates to #5342 (comment)

set up vagrant step looks flaky since last week and seems to happen more often now: https://github.com/moby/buildkit/actions/runs/10951539533/job/30525617561?pr=5343#step:7:12

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.
Error: Process completed with exit code 1.

Any idea @AkihiroSuda ?

@crazy-max
Copy link
Member Author

crazy-max commented Sep 24, 2024

seems related to hashicorp/vagrant#13501, vagrant doesn't support yet virtualbox 7.1: hashicorp/vagrant#13503

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant