Closed chimeno closed 6 years ago
Update to vagrant 2.0.2 solved the issue, I'll leave it open, but feel free to close it if it's not relevant anymore.
As it's been several months (my fault entirely) and we're now up to 2.2.0, I'll close the issue. Will take a deeper look if this comes up on any future Vagrant upgrade though.
vagrant 1.8.1 os: ubuntu server 16.04 LTS
Error: