4 ms·
On OSX Vagrant always had issues with rsync of files. If you're using vagrant as just a blank machine, there is no difference between a blank debian/jessie dock
by thepratt 9y ago
On OSX Vagrant always had issues with rsync of files. If you're using vagrant as just a blank machine, there is no difference between a blank debian/jessie docker image - apart from the lower resource usage. If you're not orchestrating anything concrete onto that vagrant box, I feel a proper workflow would be of benefit, i.e. properly reproducible builds. Take all those manual commands, prefix them with RUN in a docker file, done.
- stephenr 9y agoI think you’re describing an issue with virtual box not with Vagrant directly. You could just as easily and much more portably put those “manual steps” into a shell script and run it as a Vagrant provisioning script. If you pick the right base box you will have portability across Mac, Linux, Windows hosts, using any number of available hypervisor/ish layers (vbox, parallels, VMWare, hyperv, lxc, etc)