docker machine have his own way to create a virtualbox VM for docker
you are creating a VM with vagrant, that is fine but i believe will be separate to the VM that docker-machine will create how are you creating the VM with docker machine? or why want to create a vm with vagrant and then use docker-machine ? On Wed, Aug 21, 2019 at 9:53 PM Sorcerer Stone <[email protected]> wrote: > Hello All, > I am in Win10Pro with Hyper-V turned off. Installed Vagrant, VirtualBox, > Docker (Compose, D-Machine) ... > In the Vagrantfile, I installed bento/ubuntu-18.04 > And in the Vagrantfile script, I have the following line: > > config.vm.provider "virtualbox" do |vb| > > I assigned memory=2048 and cpus=2 > > When Vagrant Up was issued, Oracle's VirtualBox UI displaced the right > memory allocation and the right # of cpus assignments (as dictated above). > > I am having problem with running "docker-machine ip". I got error msg: > "Error getting IP address: Host is not running" > > I ran "docker-machine ls" > UI displayed the state of the driver, virtualbox, is stopped. > > But on Oracle Virtualbox interface, it said the VM for the vagrantfile is > running. So, virtualbox is not stopped, contrary to "docker-machine ls" > output. > > Then I issued inspect command: "docker-machine inspect default" > I saw something strange: > > "IPAddress": "192.168.99.101" (this is probably what I want to look for > when I typed docker-machine ip earlier) > "CPU": 1, This can't be true, as I assigned cpus=2 and the oracle > virtualbox UI also show cpus=2 > "Memory": 1024, This can't be right either, as I assigned memory to 2048 > as shown earlier and virtualbox UI also show the base memory for the > vagrant box is 2048. > > What had happened? > Could this be pointing in the direction of that my docker-compose, > docker-machine installations were done improperly? > > Thanks in advance. > > > > -- > This mailing list is governed under the HashiCorp Community Guidelines - > https://www.hashicorp.com/community-guidelines.html. Behavior in > violation of those guidelines may result in your removal from this mailing > list. > > GitHub Issues: https://github.com/mitchellh/vagrant/issues > IRC: #vagrant on Freenode > --- > You received this message because you are subscribed to the Google Groups > "Vagrant" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/vagrant-up/b7cc77de-501c-4de7-969a-d86feac1b4c3%40googlegroups.com > <https://groups.google.com/d/msgid/vagrant-up/b7cc77de-501c-4de7-969a-d86feac1b4c3%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- Alvaro -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0eybRrEYRWpZKZyg0XR93uRzBL--Z6xYRo8ZDvBDy9iZcw%40mail.gmail.com.
