Closed sthag closed 7 years ago
Hi @sthag ,
Thank you for letting me know the issue. I will check it out. Could you modify your Vagrantfile like the following to use barge v2.2.7.2 for a while?
config.vm.box = "ailispaw/barge"
config.vm.box_version = "2.2.7.2"
Best regards.
I can reproduce this issue and found the cause. I will fix it and release it right away. Thanks.
Hi @sthag,
Just released ailispaw/barge
v2.3.0.1.
Please update the box and try it.
NOTE: Don't forget to remove the line config.vm.box_version = "2.2.7.2"
before update, if you modified your Vagrantfile for the workaround.
Sorry for this inconvenience and thank you for reporting this again.
It is working ... IT IS WORKING :) Thank you very much for your immediate reaction. This way I can be productive again, lol.
Very nice to have this tool, by the way.
Thank you for using Wocker and Barge, btw. 😄
After updating the box ailispaw barge to the current version 2.3.0 I'm not able to start wocker anymore.
I see this error:
I got this the first time after executing
vagrant box update
. Afterwards I had two versions of barge. 2.3 and the old 2.2.7.2 which was running as expected before. If version 2.3 is installed every vagrant command according to wocker shows the error above. During troubleshooting I uninstalled both barge boxes. I also removed my wocker directory. I tried to install from scratch but again I get the error as described:I'm using Vagrant 1.8.7, VirtualBox 5.1.10 on Windows 10