Closed luispabon closed 8 years ago
Hi @luispabon
I've removed all shares and provisioning from your Vagrantfile:
# -*- mode: ruby -*-
# vi: set ft=ruby :
Vagrant.configure(2) do |config|
config.vm.box = "blinkreaction/boot2docker"
# Network config & shared folders
config.vm.network "private_network", ip: "192.168.33.31"
# VM definition
config.vm.provider "virtualbox" do |vb|
vb.name = "Generic PHP7"
vb.memory = 1024
vb.cpus = 1
end
end
This works without any issues on my Mac. Check this on your setup.
BWT why do you need Vagrant on Ubuntu to run docker?
We use this setup for our Mac and Windows user. Those on Linux can run containers directly.
With the default vboxsf
synced folder option, that you are using, the performance impact should be pretty bad.
Thank you @lmakarov, I'll try this shortly.
I don't run my containers on vagrant on Ubuntu, I run them directly on bare metal for the reasons you stated. Roughly 70% of phpdocker.io's visitors are either on Mac or Windows, and it's for them we also generate a Vagrantfile using blinkreaction's boot2docker box.
I'm currently adding support for NFS and SMB to PHPDocker.io.
I'm going to close this, since the issue was apparently with a custom Vagrantfile. @luispabon feel free to reopen if necessary.
I've been using your box for quite a while here over at phpdocker.io, it's been an absolute godsend. I've been experiencing the following however.
I'm not exactly sure where to report the issue as obviously this repo is for your share-optimised Vagrantfile, and the issue might be on the box itself.
Always get this error:
When I query vagrant on the machine status, it is powered off:
Vagrantfile:
Other info:
I'm not sure what information you'll need to diagnose it?