-
Notifications
You must be signed in to change notification settings - Fork 318
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
Vagrant base boxes don't exist #337
Comments
Thanks for bringing this to our attention. I was under the impression that the migration was going to happen automatically. We'll look into this over the next week. |
Great, thanks! |
The same issue here also, Download link for all secgen boxes not found. Can you please provide secgen base boxesBringing machine 'default' up with 'virtualbox' provider... If you're adding a box from HashiCorp's Vagrant Cloud, make sure the box is Name: secgen/debian_stretch_server
|
Hi @zack-r-s @krishh547 I've managed to recover our Vagrant base boxes. They should all be available again now. However, keep in mind that we are aware that the Virtualbox bases are a bit out of date. To get everything working great you should provision some VMs, and then for Debian Buster and Debian Bookworm bases it will actually pull down Debian Stretch (an older version) -- you then need to run updates on the base VM (open the VM up in your .vagrant directory) to bring it to the correct matching version of Debian. After that all the scenarios using those Debian versions (i.e. most of them) should work correctly. |
Thanks, Cliffe. Will try this. |
I have a similar problem here except I got a 501 instead of a 400:
Any updates on this? |
The project is built successfully, however, the base box for default scenario does not exist. I have tried a few scenarios with the same result. Upon checking the URL: app.vagrantcloud is migrating to Hashicorp Cloud, and the Secgen HC repo has no versions available for any of the boxes, so there is nothing to download. I have also noted that the Bookworm base module references the Stretch box in the URL. IS there a current work-around or fix planned? It seems to me that all base images now need to be build from scratch locally.
The text was updated successfully, but these errors were encountered: