Packer 1.8.4Īt some point since my last run of Packer builds version 1.8.4 was released. Even though I’ve had to revert back to VirtualBox 6.1.40, this new version of Vagrant is working fine for me. Upgrading to this didn’t cause or solve any issues for me. So my current suggestion would be use this at your own risk… Vagrant 2.3.3 It seems odd that I am getting the same result on multiple machines on two fundamentally different architectures though. I don’t know if this is just me, or if a lot of people are having problems with VirtualBox. When I revert back to VirtualBox 6.1.40, everything works as expected… This makes VirtualBox 7.0.4 unusable for me. I get the same issues on Windows 11, Windows 10 and macOS (Intel). When I saw VirtualBox 7.0.4 I was hoping this might solve my problem, but no. I’ve done all the usual firewall and antivirus stuff, and trawled the internet to see if anyone else has a solution. Also, if I attempt to use Packer, it will fail to find the kickstart file, which it attempts to access over HTTPS. I can often, but not always, start up an existing VM, but if I try to build a new VM with Vagrant it will fail to setup the networking. They all seem to come down to networking. The downloads and changelog are in the normal places.įrom my previous posts on VirtualBox 7.0.x you will know I’ve been having problems with it. I wanted to leave the rest of the post unedited, but needed to update my current situation as it has changed since this post was written… Please read the update at the bottom of this post before making any conclusions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |