Closed MikePadge closed 2 years ago
Hey @MikePadge, thanks for reporting this. I've opened PR #98 that should fix this.
Hey @MikePadge, thanks for reporting this. I've opened PR #98 that should fix this.
Welp, I feel dumb, but that did the trick. Thank you kindly.
Actually @jacobweinstock this completely breaks the docker-compose setups inside the vagrant containers, probably something to do with the extreme finicky of docker and nfs.
I can get away with nfsd, I was just looking in the wrong place, thinking I needed a vagrant nfs plugin or something I couldn't find.
Hey @MikePadge, sorry I'm not following. The PR #98 breaks the docker-compose? That PR doesn't use NFS anymore.
Debian10 Vagrant 2.2.18 Most recent sandbox
Expected Behaviour
cd sandbox/deploy/vagrant
vagrant up provisioner
- starts the sandboxCurrent Behaviour
Possible Solution
Steps to Reproduce (for bugs)
Context
Your Environment
Operating System and version (e.g. Linux, Windows, MacOS):
How are you running Tinkerbell? Using Vagrant & VirtualBox, Vagrant & Libvirt, on Packet using Terraform, or give details: Vagrant + Libvirt
I tried this on two separate servers, both debian10. Both incurred the same error.
It's late, I could have very easily overlooked something dumb, but I haven't gone out of my way to do crazy things here. Just pulled the repo and run vagrant up.